[ckan-dev] Current state of Vagrant-provisioned CKAN source installs?

Wed Dec 17 08:41:20 UTC 2014

Hi Bruce,

we use a vagrant setup for all our projects, which works pretty good. I'll
look into problems you had with https://github.com/liip/ckan-vagrant and
try to fix it.

Best Regards Stefan

On Tue, Dec 16, 2014 at 10:28 PM, Bruce Crevensten <becrevensten at alaska.edu>
wrote:
>
> Hi!  Our (small) team is happy to be moving our data distribution over to
> CKAN, and while we've gotten to a good starting point with the base
> install, we're now moving on to doing custom development to better meet our
> goals.
>
> Our preferred dev/deploy environment is to do local dev instances via
> Vagrant, keep our customizations in a Git repo and then deploy our
> customizations to production from Git.
>
> I'm aware of several Github projects that use Vagrant with either Chef or
> Puppet to automate local development builds, but alas, none of them have
> worked out-of-the-box yet for me.
>
> I'm wondering if I'm missing something simple or obvious -- or, if instead
> it's preferred to examine using Docker as a convenient way to have a local
> development instance.
>
> Guidance would be appreciated, and thanks to everyone for the ongoing
> great work on this grand tool.
>
> --
> *Bruce Crevensten*
>
>
> *Senior Software Engineer*
> (SNAP) Scenarios Network for Alaska & Arctic Planning
> www.snap.uaf.edu
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
>
>

-- 
Liip AG  // Limmatstrasse 183 //  CH-8005 Zürich
Tel +41 43 500 39 80 // GnuPG 0x7B588C67 // www.liip.ch
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20141217/e465a37a/attachment-0003.html>