Keynote: Use Vagrant - forget "works on my machine" bugs

Vagrant

If you're a developer, Vagrant will isolate dependencies and their configuration within a single disposable, consistent environment, without sacrificing any of the tools you're used to working with (editors, browsers, debuggers, etc.). Once you or someone else creates a single Vagrantfile, you just need to vagrant up and everything is installed and configured for you to work. Other members of your team create their development environments from the same configuration, so whether you're working on Linux, Mac OS X, or Windows, all your team members are running code in the same environment, against the same dependencies, all configured the same way.
Say goodbye to "works on my machine" bugs.

## Vagrant Local Dev Environment setup ---- ### Prerequisites * Install Vagrant: [https://www.vagrantup.com/downloads.html](https://www.vagrantup.com/downloads.html) * Install VirtualBox: [https://www.virtualbox.org/wiki/Downloads](https://www.virtualbox.org/wiki/Downloads) * Install Git Bash(Optional): [http://git-scm.com/downloads](http://git-scm.com/downloads) ---- ### Setup development environment 1. Open Shell (Git Bash, Cygwin) 2. Fetch or create the Vagrant repo which contains the Vagrantfile and also personal properties directory. Usually your files structure lookas like following: Vagrantfile .gitignore personal_properties backend logback.xml config-db.properties config-redis.properties ... server1 certs server.keystore conf server.conf log4j2.xml config-db.properties config-redis.properties config-hazelcast.properties server2 ... 3. Use the personal properties directory to modify the configuration files as you see fit. (e.g. db schema name in config-db.properties files server sucurite certs is needed) 4. Configure Windows firewall to allow TCP connection to needed ports *(e.g. 2000-2500, 4850, 5850 and 8080)* 5. Run Vagrant ---- ### Vagrant file If u're configuring Vagrant env from scretch and there no *Vagrant* file yet use: vagrant init It will create a new Vagrant file with the description inside. @see [Project Setup Doc](http://docs.vagrantup.com/v2/getting-started/project_setup.html) ---- ### Run Vagrant * Start up and create Vagrant boxes: vagrant up You need to be in the same folder as the *Vagrantfile* and the whole process of creating and starting up the VM-s takes a bit of time, so grab a coffee meanwhile (smile) PS! Make sure that you also check if Vagrant boxes are up to date by using the command `vagrant box outdated`. If the boxes are not up to date, issue command `vagrant box update` The Vagrant boxes come as prepackaged artifacts that the developer can download. The Vagrant boxes have version numbers which get increased with each update to the Vagrant box. Each time a new Vagrant box becomes available, the Vagrant box user get's notified and can either use the same box or update to a newer one. You can check manually if Vagrant boxes are up to date by using the command `vagrant box outdated`. If the boxes are not up to date, issue command `vagrant box update` After updating the Vagrant boxes issue `vagrant destroy` and `vagrant up`. * Check the status of virtual boxes: vagrant status * Login into virtual box: vagrant ssh <box-name> *Note: U're also able to destroy/up the certain box separately via `vagrant destroy <box-name>` & `vagrant up <box-name>`* ---- ## see Also * [Vagrant Documentation](http://docs.vagrantup.com/v2/share/) * [Keynote: AngularJS do the regular things](http://bloomlab.blogspot.com.ee/2015/09/keynote-angularjs-do-regular-things.html) * [Keynote: AngularJS basics](http://bloomlab.blogspot.com.ee/2015/09/keynote-angularjs-basic-short-notes.html) * [Tutorials Point - BestPractices](http://www.tutorialspoint.com/developers_best_practices/index.htm) * [Keynote: Top JS frmeworks 2015](http://bloomlab.blogspot.com.ee/2015/03/top-javascript-frameworks-2015.html)