Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Accepted Answer
👋🏼 @Kiva
Unfortunately this is not supported at this time. It is something we’re considering as multiple users have requested it. As a workaround you can update each component to use a different Git repo, but I realize this is not very convenient.
I am in a similar situation for which I have a “monitor worker”, which is used only to monitor and debug issues with the webserver. It would be convenient if I can turn on and off this worker independently of the working app.
This is still a problem, unless I’m missing how to trigger a single component?
I have a web service and a worker - they share a codebase as much of the code is used in both components, but I need to deploy them independently.