Question: Can a single Outpost container instance handle all roles (api, log, delivery) for dev environments?

[victorperez2911]

Question

The recommended production setup for Hookdeck Outpost suggests running three separate container instances, each with the SERVICE environment variable set to a different role: api, log, and delivery.

This setup is excellent for scalability and high availability in production. However, it's a bit too much for local development environments where simplicity is preferred.

Is it possible to run a single Outpost container instance with all three roles (api, log, and delivery) enabled simultaneously for use in development environments?

If so, how should the SERVICE variable be configured? Can it accept a comma-separated list (e.g., SERVICE=api,log,delivery) or is there another way?

Context

I'm building on a multi-tenant SaaS platform and would like to keep the local stack minimal during development while still being able to test the full Outpost behavior end-to-end.

[alexbouchardd]

SERVICE accepts all as a parameter, which starts all services within the instance! Will document better.

[leggetter]

Let's keep this open to keep track of documenting the behavior.

[alexbouchardd]

To verify, but I believe not specifying the SERVICE value will behave as all by default as well

[alexbouchardd]

Just confirming that not declaring a SERVICE value will act as all by default

[leggetter]

Work in progress solution for this in #406

[leggetter]

Closed in #406