Pablo Moreno

I don't think that we actually need separate compose and kubernetes images, all orchestrator systems should be able to operate with the same set of very granular images. So I...

I had to add the following to avoid the issue: https://github.com/galaxyproject/ansible-galaxy-extras/commit/b6c3836cae867e42b64a544692e4a24f40e64840 However is weird, because the copy is done in the docker init container: https://github.com/bgruening/docker-galaxy-stable/blob/10789e6d6ca71051d6b98e38033e49137036c00c/compose/galaxy-init/Dockerfile#L31 I guess the issue is...

Yes, that is what I meant on my previous comment.

I have made the PR so that we can close this.... unless that you want a more proper solution (I wouldn't bother and try to work ourselves out of the...

I think init is a good place to put branding and a number of other things that are unique to each instance that are difficult to inject via configuration, but...

...but that could as well happen by doing FROM the galaxy-web container I guess and putting stuff there.

Is this still active or can be used? Thanks!

I agree with @abretaud the preferred way for you to make any settings changes is to use env variables.

The compose setup is meant to be used within container orchestration setups (docker compose, kubernetes, mesos, etc), where the most typical and flexible way to inject configurations for containerised running...

You could as well use a single file with all your environment vars, BUT the whole point is that using injection of environment variables gives us the flexibility to be...