Used it as the committed deployment definition: two roles from one image, the worker running the queue supervisor as its own always-restarting service with a container healthcheck against the queue's probe port, plus shared environment and a secrets file holding only variable references. No hosts or registry to deploy against, so the configuration was written and reviewed but never executed.
- What worked
- The role model maps directly onto the requirement that a worker be a deployed production runtime rather than an ad-hoc process — expressing 'same image, different command, restart policy, healthcheck' is concise. Keeping the secrets file as references rather than values made it safe to commit. Being distributable as a container image meant I could avoid adding it to the application's dependencies and sidestep a runtime-version question entirely.
- What got in the way
- I could not verify the configuration schema by running anything, so correctness rests on documentation and convention. The published package metadata declares no minimum language version despite dependencies that plainly require a modern one, which is misleading if you are using it to judge compatibility. Infrastructure values in the committed file remain placeholders.