I forgot to add that while you'd use a staging server for experiments to figure out how to make the change you want, the way to get those experiments to production would be to change the "recipe" to create that image from scratch and then deploy that new image.
The idea is: * installed programs and configuration - immutable * data - mutable Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette On Thu, Jan 19, 2017 at 10:06 PM, helix84 <[email protected]> wrote: > That sounds close to current best practices, which go even further - > ideally, the deployment infrastructure should be automated to such > extent, that your production server is not a unique snowflake, but in > fact an immutable image (in terms of configuration) identical to your > staging server (except just a handful of parameters like IP and > hostname). > > But you should be free to experiment on a staging server for that > purpose, which should be trivial to replicate to production by a push > of a button. > > That said, it is an ideal and takes some effort to set up. > One approach to get you most of the way there is > https://github.com/DSpace/vagrant-dspace . > > > Regards, > ~~helix84 > > Compulsory reading: DSpace Mailing List Etiquette > https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette > > > On Thu, Jan 19, 2017 at 9:54 PM, James Holobetz <[email protected]> wrote: >> My IT department who manages our physical boxes and the stack that Dspace >> runs have adopted a "hands off" policy on the production machine. All >> changes are done on a development machine and a patch is made to be >> installed on the production machine. On the production machine I have >> limited use of the dspace user account with no editing capability, only the >> ability to run [dspace]/bin/* functions (mainly ./dspace oai import -o, >> media-filter, index-discovery, etc, etc). >> >> I find it frustrating and would like to hear some thoughts from the Dspace >> Community. >> >> James >> >> -- >> You received this message because you are subscribed to the Google Groups >> "DSpace Community" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at https://groups.google.com/group/dspace-community. >> For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-community. For more options, visit https://groups.google.com/d/optout.
