For those that are interested, I've created a post about my experience breaking out the tenant configuration from the mainline source code:
http://dltj.org/article/separating-configuration-code-in-collectionspace/
The practical effect is that the upstream code is mostly unchanged. (I did have to fork two of the three components in order to create a clean pull requests for the SDMoM's NAGPRA and Cultural Care work -- https://github.com/collectionspace/ui/pull/272 and https://github.com/collectionspace/application/pull/152) Feel free to use and adapt...
Peter
Peter Murray
Dev/Ops Lead and Project Manager, Cherry Hill Company
Blogger, Disruptive Library Technology Jester - http://dltj.org/
For those that are interested, I've created a post about my experience breaking out the tenant configuration from the mainline source code:
http://dltj.org/article/separating-configuration-code-in-collectionspace/
The practical effect is that the upstream code is mostly unchanged. (I did have to fork two of the three components in order to create a clean pull requests for the SDMoM's NAGPRA and Cultural Care work -- https://github.com/collectionspace/ui/pull/272 and https://github.com/collectionspace/application/pull/152) Feel free to use and adapt...
Peter
--
Peter Murray
Dev/Ops Lead and Project Manager, Cherry Hill Company
Blogger, Disruptive Library Technology Jester - http://dltj.org/