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

Galaxy configuration mechanism for WSGI/ASGI apps #10884

Closed
mvdbeek opened this issue Dec 10, 2020 · 1 comment
Closed

Galaxy configuration mechanism for WSGI/ASGI apps #10884

mvdbeek opened this issue Dec 10, 2020 · 1 comment
Labels
help wanted also "hacktoberfest", beginner friendly set of issues planning

Comments

@mvdbeek
Copy link
Member

mvdbeek commented Dec 10, 2020

Most wsgi/asgi apps can be controlled by any number of servers (uvicorn/gunicorn/hypercorn), where typically you only need to indicate the object that is the actual asgi/uwsgi app (e.g. for the app instance in app.py: uvicorn app:app).
#10823 adds a script that starts galaxy using python scripts/fapi.py -c config/galaxy.yml.

We should be able to run Galaxy with GALAXY_CONFIG_FILE=/path/to/config uvicorn galaxy:app, where GALAXY_CONFIG_FILE defaults to config/galaxy.yml

@mvdbeek
Copy link
Member Author

mvdbeek commented Mar 30, 2021

That's done with #11116

@mvdbeek mvdbeek closed this as completed Mar 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted also "hacktoberfest", beginner friendly set of issues planning
Projects
None yet
Development

No branches or pull requests

1 participant