# “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:** 4
**Page:** 1
### Author:  [@jesus2099](https://meta.discourse.org/u/jesus2099)
#### Post date: [April 27, 2016, 8:17am UTC](https://meta.discourse.org/t/easy-development-environment-creation/43306/1 "2016-04-27T08:17:40Z")
Hello,
I wanted to try and fix a one row of JavaScript code in Discourse but could not dare submit a PR without making sure I did not break anything or making sure it did really fix the problem.
So I found what was said to be the easiest way to start a Discourse dev env up: [VAGRANT.md](https://github.com/discourse/discourse/blob/master/docs/VAGRANT.md#getting-started).
In there I read:
> ### Getting Started
>
> 1. Install Git: [Redirecting…](http://git-scm.com/downloads) (or [GitHub for Windows](http://windows.github.com/) if you want a GUI)
> 2. Install VirtualBox: [Downloads – Oracle VirtualBox](https://www.virtualbox.org/wiki/Downloads)
> 3. Install Vagrant: [http://www.vagrantup.com/](http://www.vagrantup.com/) (We require Vagrant 1.7.2 or later)
> 4. Open a terminal
> 5. Clone the project: `git clone https://github.com/discourse/discourse.git`
> 6. Enter the project directory: `cd discourse`
So I followed steps 123 (I already have git and cloned a fork of discourse on my Windows laptop) and installed Virtualbox for my Windows then Vagrant for my Windows.
Until I realised, well:
- Are those steps starting from Vagrant installation shouldn’t have been done from **inside** Virtualbox?
- My Virtualbox is just empty, what OS should I put here?
- Why install git before Virtualbox if it should be inside?
I am confused.
I have done three first steps but fourth step tells me to open terminal. In Virtualbox? Which VDI?
I must be even dumber than what was expected making those _easy_ dev env install docs.
Are there some _official_ pre‐installed VDI image? Like [this seemingly outdated image](https://bitnami.com/stack/discourse/virtual-machine)?
Should the doc have been interpreted as following?
> ### Getting Started
>
> 1. Install VirtualBox: [Downloads – Oracle VirtualBox](https://www.virtualbox.org/wiki/Downloads)
> 2. Download and open this or that VDI file (which contains this or that installed OS with git)
> 3. Install Vagrant from inside VirtualBox: [http://www.vagrantup.com/](http://www.vagrantup.com/) (We require Vagrant 1.7.2 or later)
> 4. Open a terminal from inside VirtualBox
> 5. Clone your fork of the project: `git clone https://github.com/yourname/discourse.git`
> 6. Enter the project directory: `cd discourse`
From my point of view (for my low level abilities), some steps were missing. 😕
I have read both the [“ **Discourse as Your First Rails App** ” blog post](http://blog.discourse.org/2013/04/discourse-as-your-first-rails-app/) and [its comments](https://meta.discourse.org/t/discourse-as-your-first-rails-app/5751) as well.
---
### Author:  [@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")
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…
---
### Author:  [@mikechristopher](https://meta.discourse.org/u/mikechristopher)
#### Post date: [May 14, 2016, 4:35pm UTC](https://meta.discourse.org/t/easy-development-environment-creation/43306/3 "2016-05-14T16:35:16Z")
You should only need to switch on VT-x/AMD-v from within the bios. Is quite easy to do once you boot into bios
---
### Author:  [@jesus2099](https://meta.discourse.org/u/jesus2099)
#### Post date: [May 14, 2016, 10:15pm UTC](https://meta.discourse.org/t/easy-development-environment-creation/43306/4 "2016-05-14T22:15:47Z")
Thanks @mikechristopher, thanks to your terms I could find what to check [in that forum](https://forums.lenovo.com/t5/ThinkPad-T400-T500-and-newer-T/Enable-VT-x-in-bios-on-T420s/td-p/642461) because where I had looked before it said Hyperthreading activated but now that I know it is is weird place like **Security** / Virtualisation I was able to see that it was indeed deactivate.
Unfortunately I am in read only mode as my company IT is understandably keeping password away from us, users.
I will try to make it switched on…