Task #11320 (new)
Opened 11 years ago
Last modified 9 years ago
Fix behaviour of OMERO-qa-upgrade.py on first run — at Initial Version
| Reported by: | spli | Owned by: | spli |
|---|---|---|---|
| Priority: | minor | Milestone: | 5.x |
| Component: | General | Version: | 4.4.8 |
| Keywords: | n.a. | Cc: | jamoore, sbesson |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | Testing and Docs (1) |
Description
If the OMERO-CURRENT symlink doesn't exist the upgrade script fails. What's the appropriate behaviour? If this is a completely new installation the database and datastore need to be created and configured.
A related issue is whether the CFG variable should be enabled by default: https://github.com/ome/omero-setup/blob/f39bdc3f484e2a432205e6f0eb4013839a874a82/OMERO-qa-upgrade.py#L60
My feeling is it shouldn't since if someone has a random config.xml file in their home dir it could wipe out their existing config.
Assuming the main use-case for CFG is a new server installation against an existing database/datastore how about we only create a non-existant SYMLINK if CFG is also defined?
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
