# “Easy” development environment creation

**URL:** https://meta.discourse.org/t/easy-development-environment-creation/43306
**Category:** Development
**Created:** [April 27, 2016, 8:17am UTC](https://meta.discourse.org/t/easy-development-environment-creation/43306 "2016-04-27T08:17:40Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![jesus2099](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jesus2099/32/119720_2.png) [@jesus2099](https://meta.discourse.org/u/jesus2099)
#### Post date: [May 14, 2016, 4:09pm UTC](https://meta.discourse.org/t/easy-development-environment-creation/43306/2 "2016-05-14T16:09:50Z")

</div>

Well in fact it is just as said, the commands must be launched not from within Virtualbox but maybe I could have been helped by having a few words more in that step by step.

I was actually trying to locally test a revert of row number 176 in [this helpful fix](https://meta.discourse.org/t/open-all-external-links-in-a-new-tab-option-does-not-work-for-protocol-agnostic-links/42224/23) where it seemed that [row 176 change](https://github.com/discourse/discourse/commit/6ee11adf58d247d004ed838520d99281ce6426cb#diff-0b8b23466c30d9971f312535feee3b6aL176) was not necessary and I got a regression appear in Opera Presto around that very same moment: now internal links open in new tab.

So I was unlucky trying to instal a local Discourse because

- my professional PC on Windows 7 can build the image with Vagrant but VirtualBox cannot run VM in 64 bit mode or something like that which requires BIOS access or something.
- my own PC on Windows XP SP3 cannot run Vagrant (but it can run VirtualBox in 64 bit mode, albeit very slowly but NP).

Maybe I should try and generate image on pro PC and then run it on own PC but it is all scripted and I don’t know how much I can interfere in the middle of the process…

---

_[View the full topic](https://meta.discourse.org/t/easy-development-environment-creation/43306)._
