-
Notifications
You must be signed in to change notification settings - Fork 991
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.
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
Bring Galaxy, reports, and shed run scripts in sync. #2837
Conversation
- They now uniformly handle server option processing. - Reports and Tool Shed now respect many new and important options such as --skip_venv. - Reports and Tool Shed now do extra checking around Python version that Galaxy does. In addition to improving the reports and tool shed startup scripts and reducing cognative load with respect to option handling, this is an important pre-condition to us being able us to switch on uwsgi by default for all three services simultaneously without a bunch of copy and pasting.
Includes #2836 but that should disappear once that PR is merged I believe. |
Initial outline of allowing launch via uwsgi.
These were removed from Galaxy's config a while ago.
This seems to break (at least) reports running for me. With reports running locally (from dev), After killing it manually and trying to relaunch (from this branch) |
Thanks for the review @dannon - I'll fix and reopen. |
@jmchilton Sounds good. (or, really, it'd be fine to fix them here on this branch to preserve the context, but totally up to you) |
--skip_venv
.In addition to improving the reports and tool shed startup scripts and reducing cognative load with respect to option handling, this is an important precondition to us being able us to switch on uwsgi by default for all three services simultaneously without a bunch of copy and pasting.