Not something my work needs so will do this on my own time, but now that we have an automated build of our 'californica' Hyrax application it would be nice to set up a nightly build of the new 'nurax' app too.
I've made some changes for 'californica' that have probably broken the Nurax build (mainly in the .env configuration). Fixing those will also make the project more robust for different Hyrax apps (at least in that some of the areas of difference can be documented or perhaps some best practices established for naming db variables, etc.)
nurax-dev.curationexperts.com is auto-building from https://github.com/samvera/hyrax/ master branch now. That's the one to use. I may have to rewrite some of the stuff I was originally doing in my fork(?)
Not something my work needs so will do this on my own time, but now that we have an automated build of our 'californica' Hyrax application it would be nice to set up a nightly build of the new 'nurax' app too.
I've made some changes for 'californica' that have probably broken the Nurax build (mainly in the .env configuration). Fixing those will also make the project more robust for different Hyrax apps (at least in that some of the areas of difference can be documented or perhaps some best practices established for naming db variables, etc.)