We do need to include some kind of worker id in the server_name. If we
don't do this and we start with multiple workers the internal
QueueWorker won't work and multiple processes can pick up the same job
if the web process is also a job handler.
If the database is combined, running `./manage_db.sh upgrade` should upgrade
BOTH models: gxy and tsi. However, if tsi uses a separate database, only
the galaxy model should be updated.
Also, see this for context: https://github.com/galaxyproject/galaxy/pull/13108#discussion_r789108576
See inline comments for more details.
The new tests are examples of new behavior.
All refactoring is directly related to the changes in this commit.
- Preserves usage of legacy script while not hiding the Alembic script.
(see manage_db.sh and run_alembic.sh)
- Adds documentation (see top of script files)
- Includes misc. relevant refactorings
- Includes unit tests for testing legacy script handling
Also add exec permissions to create/migrate python scripts.
(not sure this is required, adding for consistency with previous
version)
+ A few fixes for TS scripts, tests
Squashed:
- pick b62443245e Add create/migrate scripts for Alembic dbs
- squash 06f0a923ca Fix integration test (test only relevant for TS)
You'll be running into problems later on anyway, and it doesn't look
like there are builds with known shasums anymore for more recent
virtualenv zipapps.
For VCS references, need to specify the branch if it's not `master`.
Also:
- Update Poetry download link
- Require pip >= 19.3 to support direct references as requirement
specifiers
https://www.python.org/dev/peps/pep-0440/#direct-references
their own means of setting a log file. Read the supervisor log if it
exists and the daemon log does not, since failure to start Galaxy will
prevent creation of the daemon log file.
When running first startup in CI, attempt to read log files from
multiple places to make debugging different types of failures possible.
mvdbeek