# (Sostituito) Configura un ambiente di sviluppo usando Vagrant su Ubuntu

**URL:** <https://meta.discourse.org/t/superseded-set-up-a-development-environment-using-vagrant-on-ubuntud/45277>\
**Category:** Development\
**Tags:** how-to\
**Created:** [5 Giugno 2016, 2:54pm UTC](https://meta.discourse.org/t/superseded-set-up-a-development-environment-using-vagrant-on-ubuntud/45277 "2016-06-05T14:54:07Z")\
**Posts on this page:** 1\
**Showing post:** 23

<div class="post-metadata">

**Author:** ![tarek](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tarek/32/124831_2.png) [@tarek](https://meta.discourse.org/u/tarek)\
**Post date:** [31 Ottobre 2018, 6:19pm UTC](https://meta.discourse.org/t/superseded-set-up-a-development-environment-using-vagrant-on-ubuntud/45277/23 "2018-10-31T18:19:17Z")

</div>

Thank you for the advice. I’ll look at how to do this more rationally when I have a bit of time for it. In the meantime, I managed to [fix my plugin](https://meta.discourse.org/t/allow-reply-to-individual-instead-of-topic-forum-mailing-list-feature/44905), so glad I was at least able to get the environment going. If nothing else, the familiar Vagrant is ideal for idiots like me who want to drop in very occasionally without learning a new dev setup.

---

_[View the full topic](https://meta.discourse.org/t/superseded-set-up-a-development-environment-using-vagrant-on-ubuntud/45277)._
