Title: Message Title
|
|
|
|
|
Issue Type:
|
![Code Task]() Code Task
|
|
Assignee:
|
Unassigned
|
|
Components:
|
vagrant-dspace
|
|
Created:
|
06/Nov/13 4:23 PM
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Hardy Pottinger
|
|
As developers, we all have our own itch to scratch when it comes to working with DSpace, and our own preferences for how we like our development environment to be set up. To facilitate that level of customization, we should add a optional shell provisioner to the Vagrantfile in Vagrant-DSpace, which will only be run if present.
A bonus of this approach is it keeps local customizations simple, if you can write a BASH script, you can customize your installation of Vagrant-DSpace. You don't need to be an expert in Puppet scripting.
It also keeps local concerns, and "vagrant-isms" out of our Puppet code, which will help with further generalizing that Puppet code, for other deployment purposes.
I have tested this idea and have code ready to merge. I will make a PR later today.
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
