Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

omego --omerosql option exposure #4

Open
dpwrussell opened this issue Jul 21, 2017 · 1 comment · May be fixed by #19
Open

omego --omerosql option exposure #4

dpwrussell opened this issue Jul 21, 2017 · 1 comment · May be fixed by #19
Assignees
@manics

Comments

@dpwrussell
Copy link
Member

dpwrussell commented Jul 21, 2017 •
edited

I am currently overriding the 60-database.sh startup file completely because in my case I may be restoring a database rather than creating a new one from scratch. Building from a specific SQL file might be a useful thing to be able to do in general though (e.g. for diagnosing a server where you have been given a dump) and I could also make use of that.

omego has an option --omerosql which does exactly that, but the question would be: How to expose that at container instantiation time. A simple way would be to designate a place where a SQL file could be placed using a volume mount (or other technique, in my case an earlier startup script might have fetched it to the prescribed location from S3), and if present will be used instead of creating a fresh database if that file exists.

Any thoughts?
@dpwrussell
Copy link
Member Author

E.g. https://github.com/dpwrussell/omero-server-docker/tree/sql-file

Name of the file could be fixed, controlled by an environment variable or both.

The logic of the upgrade could also be rearranged if made slightly more complicated. e.g.

  • Check for an existing database
    • If no existing database, check for sql file.
      • If sql file, load it
      • If no sql file, initialize database
  • Check if upgrade is required (not necessary in init case of course)

@joshmoore joshmoore mentioned this issue Nov 27, 2017
Merged
@joshmoore joshmoore linked a pull request Feb 19, 2018 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@manics manics

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

SQL backup/restore (WIP) joshmoore/omero-server-docker
2 participants
@manics @dpwrussell