24.2 is coming

[bgruening]

No description provided.

[kysrpex]

Regarding your comment on usegalaxy-eu/issues#422; the old configuration setting still works and when provisioning the image gx_it_proxy_version is set to '>=0.0.6', so the new version should be automatically installed and it should just work.

However, is it possible to run multiple instances of this Docker image that share a common database? Then I think I'd have to make changes.

[bgruening]

No this is not possible. It is strictly not needed to use PG for the proxy for this project. I just thought its a good thing to do. Isn't the new way the way we would like to advertise/recommend?

[kysrpex]

Isn't the new way the way we would like to advertise/recommend?

Maybe only if a high-availability setup is needed, right? It requires extra setup (creating a dedicated database and enabling PostgreSQL asynchronous notifications for the gxitproxy table), yet if there is only a single instance of Galaxy running it provides no benefit back in exchange.

Given that it is not a high-availability setup, using PostgresSQL for the proxy within this Docker image does not provide an advantage in itself, but still means more lines of code within the repository to write and maintain.

The Galaxy Docker Image is an easy distributable full-fledged Galaxy installation, that can be used for testing, teaching and presenting new tools and features.

If it is because of demonstrating and presenting the new feature: the GTN training was updated; the release notes for 24.2 also mention the feature; and the README for the proxy shows how to use it. Is it really still worth it to promote it by making the setup part of this Docker image? If you insist, it can still be done ofc