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

Thu Jan 29 21:06:24 UTC 2015

Sure would help if I included a link to our code, huh?

*https://github.com/ua-snap/ckan-puppet-centos
<https://github.com/ua-snap/ckan-puppet-centos>*

There we go!

On Thu, Jan 29, 2015 at 12:04 PM, Bruce Crevensten <becrevensten at alaska.edu>
wrote:

> Hi all, just closing the loop on this -- thanks very much for the various
> references, they were indeed helpful!
>
> Since our organization runs CentOS and Puppet, we decided to take the
> excellent work done on the Puppet Forge module
> <https://forge.puppetlabs.com/conzar/ckan> and modify it to run on CentOS.
>
> What we've got is not a thing of beauty, but it does successfully
> provision a Centos 6.5 image with CKAN with spatial and harvester
> extensions, and we're able to use it to continue development.
>
> Thanks again for the help!
>
> On Wed, Dec 17, 2014 at 8:00 AM, Alice Heaton <a.heaton at nhm.ac.uk> wrote:
>
>>  Hi,
>>
>> Another one:
>>
>> https://github.com/NaturalHistoryMuseum/dataportal-server-provision
>>
>> It includes our vagrant file and our bash provisioning scripts. It's very
>> specific to our setup (and includes more than ckan), but hopefully it can
>> be good for inspiration :-)
>>
>> Cheers,
>> Alice
>>
>>
>> On 16/12/14 21:28, Bruce Crevensten 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 listckan-dev at lists.okfn.orghttps://lists.okfn.org/mailman/listinfo/ckan-dev
>> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
>>
>>
>>
>> _______________________________________________
>> 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
>>
>>
>
>
> --
> *Bruce Crevensten*
>
>
> *Senior Software Engineer*
> (SNAP) Scenarios Network for Alaska & Arctic Planning
> www.snap.uaf.edu
>

-- 
*Bruce Crevensten*

*Senior Software Engineer*
(SNAP) Scenarios Network for Alaska & Arctic Planning
www.snap.uaf.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20150129/7de111ca/attachment-0003.html>