SQL backup/restore (WIP) #19
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
omego assumes that the DBHOSE and DBNAME are set via bin/omero config. DBNAME was previously *not* set to prevent an accidental upgrade of a database. Here we set DBNAME only if the database has not been created elsewhere.
|
Conflicting PR. Removed from build DOCKER-merge#296. See the console output for more details.
--conflicts |
5 tasks
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix gh-4
Includes @dpwrussell
sql-filebranch.Currently a work-in-progress as I investigate various backup/restore scenarios. With an upcoming dependency on Ansible 2.4 I'll likely make use of ansible/ansible#20627 by having a playbook available in the container for export.