Conversation
|
Regarding your comment on usegalaxy-eu/issues#422; the old configuration setting still works and when provisioning the image 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. |
|
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? |
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 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.
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 |
systemctl daemon-reload
systemctl start cvmfs-reload
instead of:
if [ -d /var/run/cvmfs ]; then
cvmfs_config reload
fi
in the "postinst" scripts. In the container we do not have systemctl installed.
bgruening
force-pushed
the
24.2
branch
2 times, most recently
from
55876cb to
c6646eb
Compare
|
cvmfs_2.12.4~1+ubuntu22.04_amd64.deb is broken for non systemd systems. The problem seems to be known a new package will be released soon. |
2 participants
No description provided.