Task #11320 (closed)
Opened 11 years ago
Closed 9 years ago
omego init command to install OMERO
| Reported by: | spli | Owned by: | spli |
|---|---|---|---|
| Priority: | critical | Milestone: | 5.x |
| Component: | Deployment | 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: | n.a. |
Description (last modified by spli)
Old 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?
Change History (5)
comment:1 Changed 11 years ago by spli
- Component changed from General to Deployment
- Description modified (diff)
comment:2 Changed 11 years ago by spli
- Sprint changed from Testing and Docs (1) to Testing and Docs (2)
comment:3 Changed 11 years ago by spli
- Cc jamoore sbesson added
- Description modified (diff)
- Priority changed from minor to critical
- Summary changed from Fix behaviour of OMERO-qa-upgrade.py on first run to omego init command to install OMERO
comment:4 Changed 11 years ago by jamoore
- Sprint Testing and Docs (2) deleted
Referencing ticket #11363 has changed sprint.
comment:5 Changed 9 years ago by spli
- Resolution set to fixed
- Status changed from new to closed
Closing, handled in Trello.
Referencing ticket #11217 has changed sprint.