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

Roadmap to FastAPI #12257

Closed
28 of 32 tasks
Tracked by #11824 ...
mvdbeek opened this issue Jul 14, 2021 · 8 comments
Closed
28 of 32 tasks
Tracked by #11824 ...

Roadmap to FastAPI #12257

mvdbeek opened this issue Jul 14, 2021 · 8 comments
Assignees
Labels
Milestone

Comments

@mvdbeek
Copy link
Member

mvdbeek commented Jul 14, 2021

I will update this as we go along.

@mvdbeek mvdbeek added this to the 21.09 milestone Jul 14, 2021
@natefoo
Copy link
Member

natefoo commented Jul 20, 2021

https://docs.galaxyproject.org/en/master/admin/special_topics/interactivetools.html (can I convince @hexylena or @natefoo to take this on ? It may include adding the nodejs proxy to the circusd config)

Yes.

@jmchilton jmchilton changed the title Roadmap to fastAPI in 21.09 Roadmap to fastAPI in 22.01 Sep 2, 2021
@mvdbeek mvdbeek modified the milestones: 21.09, 22.01 Sep 28, 2021
@mvdbeek
Copy link
Member Author

mvdbeek commented Dec 14, 2021

@natefoo @dannon
I'm working on removing all the uwsgi/paster cruft (https://github.com/galaxyproject/galaxy/compare/dev...mvdbeek:drop_wsgi_mode?expand=1) and updating run.sh, and ran into one thing I should've thought about but didn't ... do we want to provide a circusd instance per thing (galaxy, toolshed, reports) ? That seems like the only way we can just do ./run.sh or ./run_tool_shed.sh without coordinating which services to start. Or are we ok with one circusd just for Galaxy, and the rest will continue to start the process directly ? I guess I'd prefer that since it's less work, but I think we need a cron-style task for the tool shed already ... or I'll have to refactor that one toolshed cron task which I don't think has to be a cron task in the first place ...

@natefoo
Copy link
Member

natefoo commented Dec 22, 2021

We have discussed this some on matrix, but for the record, I'm not really concerned about the other applications, fwiw. We actively discourage anyone from running a TS, so reports is the only question here, which many production servers also do not run. We could allow people to optionally run it from the Galaxy supervisor I guess?

@mvdbeek
Copy link
Member Author

mvdbeek commented Mar 15, 2022

Alright, made a lot of progress, and the remaining tasks we can do in the 22.05 cycle

@mvdbeek mvdbeek modified the milestones: 22.01, 22.05 Mar 15, 2022
@nsoranzo nsoranzo changed the title Roadmap to fastAPI in 22.01 Roadmap to FastAPI Mar 15, 2022
@nsoranzo
Copy link
Member

Q: Should we drop merge_duplicate_keys=True from _order_load_path() in lib/galaxy/config/config_manage.py ? It was needed because uWSGI's YAML config allowed duplicated keys. But if we drop it, I think we cannot simply ignore the uwsgi: section of migrated galaxy.yml files, but we would need to ask admins to remove it, otherwise parsing may fail.

@mvdbeek
Copy link
Member Author

mvdbeek commented Mar 22, 2022

But if we drop it, I think we cannot simply ignore the uwsgi: section of migrated galaxy.yml files, but we would need to ask admins to remove it, otherwise parsing may fail.

I think we should slightly restructure the file. For the conversion path I think it's fine if we rewrite the config file without the uwsgi section, for the validation part it's fine to raise a validation error.

@mvdbeek mvdbeek self-assigned this Mar 24, 2022
@mvdbeek mvdbeek modified the milestones: 22.05, 22.09 Jun 28, 2022
@bgruening
Copy link
Member

Impressive work! I guess we can close this?

@mvdbeek
Copy link
Member Author

mvdbeek commented Aug 15, 2022

I think there's a little bit of docs left to do, I'll look over this

@dannon dannon modified the milestones: 23.0, 23.1 Feb 7, 2023
@mvdbeek mvdbeek closed this as completed Jul 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants