liip/ckan-vagrant

Name: ckan-vagrant

Owner: Liip

Description: Vagrant based CKAN development environment

Created: 2014-09-04 12:19:34.0

Updated: 2018-03-05 02:52:09.0

Pushed: 2015-06-23 19:20:31.0

Homepage: null

Size: 257

Language: Ruby

GitHub Committers

UserMost Recent Commit# Commits

Other Committers

UserEmailMost Recent Commit# Commits

README

Vagrant CKAN development environment

CKAN Version: 2.3

Requirements
Virtualbox
vagrant up

Add the Vagrant box's IP address to your hosts file:

172.94.43.196   ckan.lo
Docker

Vagrant supports Docker natively from Version 1.6 on.

You have to add permissions for the vagrant user (uid 1000) to the shared folder ckan-vagrant:

setfacl -R -m u:1000:rwX .

Then you can bring the box up:

vagrant up --provider=docker

To find out the IP Address of the box, use the container name that Vagrant prints out (in my case ckan-vagrant_default_1409916413) with docker inspect:

docker inspect --format '{{ .NetworkSettings.IPAddress }}' ckan-vagrant_default_1409916413

See Switching providers if you work with different providers.

Digitalocean
Install the required Vagrant plugins
vagrant plugin install vagrant-digitalocean
vagrant plugin install vagrant-omnibus
Setup the Digitalocean keys

Copy digitalocean.json.dist to digitalocean.json and add the client id and the API key Uncomment the relevant lines in the Vagrantfile.

Fire it up
vagrant up --provider=digital_ocean
Switching providers

“Vagrant currently allows each machine to be brought up with only a single provider at a time”. That means you cannot do vagrant up with virtualbox and then withdigitalocean. Quite a simple fix for that is to rename the .vagrant folder to e.g. .vagrant.digitalocean. Running vagrant up after that will create a new folder that contains the virtualbox specific config and you can switch by renaming the folders.


This work is supported by the National Institutes of Health's National Center for Advancing Translational Sciences, Grant Number U24TR002306. This work is solely the responsibility of the creators and does not necessarily represent the official views of the National Institutes of Health.