Galaxy deployment options

[sebastian-luna-valero]

Hi @micafer

@bgruening is currently updating the docker-galaxy repository.

I see there are different templates and artifacts in IM (including an Ansible role) to deploy Galaxy and I am opening this thread to discuss how to converge/update the available options to deploy Galaxy with IM.

Initially I am testing the docker-compose TOSCA template in IM to deploy galaxy using docker-compose.

However, we may want to add new TOSCA templates to give Galaxy users the option to configure certain parameters.

What do you think?

[micafer]

It is a good idea.

[bgruening]

The ansible deployment is most likely more scalable I would assume. The single-docker container is meant for smaller groups or single-user deployments.

The cool thing with this container is, we can configure it completely with ENV vars. So if we could allow to set ENV vars in the form this would give this container a LOT of flexibility already.

[sebastian-luna-valero]

Thanks both.

@bgruening the main idea with this repo is to serve smaller groups and/or single-user deployments, right? In other words, should we then focus on the docker-compose deployment or on the ansible deployment?

Indeed we can configure the TOSCA template to capture user input and put them in ENV vars for the deployment of the container.