This enables organisations to run multiple instances of Pretzel in parallel, for separate species, research groups, and software versions.
Merge & Release Pipeline :
establish a 2nd dirac pretzel server for presentation and testing of UG prototypes
Summary of status of feature/upgradeFrontend2 as a 2nd dirac pretzel server :
The pretzel image build needed rollup, which I solved, and now a node-sass version issue - will work on that.
Running from the command-line is not authenticating the mongoDb connection successfully - I'm working on this also.
The main complications on dirac atm are that dirac mongoDb requires authentication, and git operations are restricted to a particular URL form, and I haven't been able to configure that to work in the dependencies which we get from github (most dependencies are from npm), which causes npm install to fail.
The authentication may have changed during the dirac update or more likely a package dependency update, or it may be that the configuration I am using to run as a second server is not setting up the authentication correctly; I don't think it is the latter because the mongoDb server log shows
0a35824
update repository.url in package.json to reflect fork
copied mongo database dirac pretzel to pretzel2
add user pretzelUser to both those databases and change authSource from admin to pretzel or pretzel2;
it is probably possible to authenticate successfully using authSource:admin, but it probably suits our purpose to define the user in the pretzel database instead of admin, i.e. the user list will be associated with the data.
feature/upgradeFrontend2 running OK as a 2nd dirac pretzel server on /pretzelUpdate
except that some API requests are missing / i.e. pretzelUpdateapi instead of pretzelUpdate/api
[ ] ensure there is a / between ROOT_URL and 'api' in the URL used for remaining API requests
[x] missing / when using ROOT_URL in login :
https://.../pretzelUpdate/login
Cannot POST /pretzelUpdateapi/Clients/login # should be /pretzelUpdate/api/Clients/login
This enables organisations to run multiple instances of Pretzel in parallel, for separate species, research groups, and software versions.
Merge & Release Pipeline :
Summary of status of feature/upgradeFrontend2 as a 2nd dirac pretzel server : The pretzel image build needed rollup, which I solved, and now a node-sass version issue - will work on that. Running from the command-line is not authenticating the mongoDb connection successfully - I'm working on this also.
The main complications on dirac atm are that dirac mongoDb requires authentication, and git operations are restricted to a particular URL form, and I haven't been able to configure that to work in the dependencies which we get from github (most dependencies are from npm), which causes npm install to fail. The authentication may have changed during the dirac update or more likely a package dependency update, or it may be that the configuration I am using to run as a second server is not setting up the authentication correctly; I don't think it is the latter because the mongoDb server log shows
copied mongo database dirac pretzel to pretzel2
add user pretzelUser to both those databases and change authSource from admin to pretzel or pretzel2; it is probably possible to authenticate successfully using authSource:admin, but it probably suits our purpose to define the user in the pretzel database instead of admin, i.e. the user list will be associated with the data.
feature/upgradeFrontend2 running OK as a 2nd dirac pretzel server on /pretzelUpdate except that some API requests are missing / i.e. pretzelUpdateapi instead of pretzelUpdate/api