# Rapidly deploying Ignition environments on Industrial PCs

**URL:** <https://forum.inductiveautomation.com/t/rapidly-deploying-ignition-environments-on-industrial-pcs/14894>\
**Category:** General Discussion\
**Created:** [July 26, 2017, 6:32pm UTC](https://forum.inductiveautomation.com/t/rapidly-deploying-ignition-environments-on-industrial-pcs/14894 "2017-07-26T18:32:09Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![nmudge](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nmudge/32/3394_2.png) [@nmudge](https://forum.inductiveautomation.com/u/nmudge)\
**Post date:** [July 26, 2017, 6:49pm UTC](https://forum.inductiveautomation.com/t/rapidly-deploying-ignition-environments-on-industrial-pcs/14894/2 "2017-07-26T18:49:27Z")

</div>

You could use an approach like the Vagrant setup made by @Kevin.Collins. See this forum post: [Vagrant-based Ignition Development VM](http://forum.inductiveautomation.com/t/vagrant-based-ignition-development-vm/14873)

---

_[View the full topic](https://forum.inductiveautomation.com/t/rapidly-deploying-ignition-environments-on-industrial-pcs/14894)._
