Closed hajaalin closed 6 years ago
Hi @hajaalin, that's like a good suggestion. One reason I didn't originally do that is because omero-server and omero-web are using the same config, and I didn't want to restart the server (can take several minutes) for a web-only config change (should be quick), but now that there's some work on decoupling the omero.web installation this change should be fine. I'll open a PR later.
Following up #119 There's a few issues to think about such as
Hi @manics, I'm now working on LDAP setup, and after those config changes it seems necessary to restart the server. I added a handler to do this using "service" module. I also added a handler to reset the old config, but I'm not sure how safe this is. If something goes wrong in the next handler that sets the new config, the server might be left without db connection settings for example.
Also related to LDAP, I added an option to set up trust store. This also needs a server restart to take effect.
This should be handled in https://galaxy.ansible.com/openmicroscopy/omero-server/
Configuration changes made in Ansible do not seem to be propagated to an installed server. I installed a test server with training-server.yml, and afterwards set
and ran the playbook again. The change shows up in a config file, but not in "omero config"
Looking at
roles/omero-server/tasks/main.yml
, it seems that onlyomego install
andomego upgrade
use this configuration. Maybe there could also be a handler to runomero config set
whenomero-base.config
oromero-additional.config
are changed?