Additional flavors apart from dev and prod?

[akulmehta]

I am making an app which I am hoping to open source so that others can use it to self host this application. I would therefore like the ability to have different flavors of docker-compose files apart from the dev and prod versions, with either additional services or different configurations. Is it possible to tell spin to use specific docker-compose files?

[jaydrogers]

spin up will default to docker compose up -f docker-compose.yml -f docker-compose.dev.yml.

You could change with with $SPIN_ENV

That means if we set SPIN_ENV to "other", it would run this:

# Command
SPIN_ENV=other spin up

# Output of what would run
docker compose up -f docker-compose.yml -f docker-compose.other.yml

Few notes

• In CI/CD, I just run raw docker compose commands
• I almost never change SPIN_ENV, because all developers work off dev
• For running

I know you've asked about how to run pre-compiled applications before. I have LOTS of things that I will need to create content on, but it's totally possible.

We intend to release a SaaS as self hosted, all running on Spin 😃

I will have more content on this through 2025 👍