Predictable container names and network #1661
DiiiaZoTe
started this conversation in
New Features
Replies: 1 comment 1 reply
-
This would be really nice but it also creates an implicit dependence on coolify's behaviour in downstream scripts that might (or might not) use this naming to perform different actions so it would eventually have to be versioned just like API changes. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
When deploying a ressource using GitHub app, either public or private. It would be nice to have a name and network field to set the name and the network of the container. Right now, we have absolutely no visibility on the container.
Use case:
Let's say we own 2 domains, example.io and example.com.
Our app is example.io then we could do rewrites or redirects for example.com to example.io
One could say why don't you containerize the app yourself and just deploy everything using a docker compose... I could but I don't want to have to setup a pipeline to containerize the app every time I push a change.
Beta Was this translation helpful? Give feedback.
All reactions