path: root/vagrant
Commit message (Collapse)AuthorAgeFilesLines
* Fix bootstrapping vagrant environment.Harald Eilertsen2018-04-011-1/+1
| | | | | | | - just start postgresql instead of restarting everything after install. - update setup script to install required ruby version and deps if not installed. - seed database when running the dev:setup rake task.
* Upgrade Vagrant setup for FreeBSD 10.4, and bring back rbenv.Harald Eilertsen2018-03-311-1/+3
* vagrant: Install dependency nodejs.Harald Eilertsen2017-12-261-1/+1
* Add imagemagick-nox11 to vagrant box for image processing.Harald Eilertsen2017-12-171-1/+1
* vagrant: Install sqlite3, drop nginx.Harald Eilertsen2017-12-101-2/+1
| | | | | We have sqlite3 as a development dependency for some reason. Don't really need nginx for the dev setup.
* The vagrant box needs git.Harald Eilertsen2017-12-041-1/+1
* Reboot vagrant integration.Harald Eilertsen2017-12-041-11/+8
| | | | | Use FreeBSD 10.3, and a setup more similar to what we have on the production server. Just installing basic dependensies for now.
* Install imagemagick in vagrant vm.Harald Eilertsen2014-02-161-1/+1
* Add vagrant setup to make deploying dev env easier.Harald Eilertsen2014-01-112-0/+24
Run 'vagrant up' to bootstrap the environment. The first time you do this, takes quite some time as it will download the base image, and provision it for the dev environment. Onse up you should be able to log in the the dev website by pointing your web browser to localhost:4567. The first time you will have to register a new user, and off you go. Run 'vagrant halt' to stop the vm. Next time you restart it using 'vagrant up' it should boot a lot faster, since the provisioning is already done. Run 'vagrant destroy' to clean up the VM and reclaim any disk space used by it. This will not remove the base image, only the instance in this dev environment. Notice: Due to a problem, the dev web server fails to start when doing a 'vagrant up' after the initial provisioning. To overcome this issue the following commands and you should be fine again: vagrant ssh sudo systemctl start rails logout Now wait a few seconds and the web server should respond again. I'll try to fix this problem later. requires vagrant and VirtualBox to work. See http://www.vagrantup.com for instructions on how to install vagrant for your system.