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.

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

Closed
wants to merge 6 commits into from

Conversation

jmchilton
Copy link
Member

  • They now uniformly handle server option processing.
  • Reports and Tool Shed now respect many 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 precondition to us being able us to switch on uwsgi by default for all three services simultaneously without a bunch of copy and pasting.

- 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.
@jmchilton jmchilton added kind/enhancement kind/refactoring cleanup or refactoring of existing code, no functional changes status/review area/scripts labels Aug 22, 2016
@jmchilton
Copy link
Member Author

Includes #2836 but that should disappear once that PR is merged I believe.

@galaxybot galaxybot added this to the 16.10 milestone Aug 22, 2016
@dannon
Copy link
Member

dannon commented Aug 23, 2016

This seems to break (at least) reports running for me. With reports running locally (from dev), ./run_reports.sh --stop-daemon is returning a [1] and is not stopping reports.

After killing it manually and trying to relaunch (from this branch) ./run_reports.sh --daemon simply hangs instead of daemonizing and running reports.

@jmchilton
Copy link
Member Author

Thanks for the review @dannon - I'll fix and reopen.

@jmchilton jmchilton closed this Aug 23, 2016
@dannon
Copy link
Member

dannon commented Aug 23, 2016

@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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/scripts kind/enhancement kind/refactoring cleanup or refactoring of existing code, no functional changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants