Don't trigger a new build when an application is resumed
planned
d
danielle
Sometimes there's a need to suspend and then resume a service (for example, when performing maintenance actions like migrations). This is inconvenient when Render triggers a new build when the service is resumed.
Log In
k
kyle
I think this speaks to a bigger issue which is a general improvement in how containers are managed through render.
For one, it would be great if render had it's own container registry (or a very streamlined integration with a 3rd party). And then supported a host of features around the management and orchestration of these containers where you could stage, run/replace containers in a certain order, pause, kill, restart, etc.
Render feels very much locked into this paradigm of "you ship code and we do the rest", which is great for a single/simple app but when you have many intertwined services it makes more sense for actions to be taken directly on containers. If render build a solid GUI with a technology such as temporal.io it would be really powerful and a big step in the right direction.
Anurag Goel
planned
M
Maximiliaan Strother
Best if this was a toggleable setting! :>