-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support multiple compose files #147
Comments
@wjensen-godaddy thanks, I'm curious about your use case and whether it could be better solved with, for example, stage parameters in Compose config. Could you share what is different between the files between dev and other stages? |
@mnapoli For sure. This is what we need in prod:
And this is what we need locally and in dev:
We also support spinning up a deploy for each PR. And we want to give devs the options to deploy the full stack, or the skinny version. Like you say, maybe there's a better way to support that than multiple config files? |
We've also had some proposals that you could deploy only specific services - #35 |
@pgrzesik Possibly. Although if I filtered out |
Oh right, I've missed that part there, thanks for correction @wjensen-godaddy 👍 |
Another idea I had, is when issuing service specific commands, missing dependencies could be a warning instead of an error. That way I could run My current workaround, is I run |
any news about specific compose config? |
Is there an existing issue for this?
Use case description
The services I need to run vary depending on the environment: local, dev, prod.
Proposed solution (optional)
It would be nice if I could have a config file for each of them, and then a way to tell serverless which one to use. Perhaps something like:
serverless deploy --config=serverless-compose-dev.yml
The text was updated successfully, but these errors were encountered: