Skip to content
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

Allow using a single env template for multiple outputs #351

Closed
Zeko369 opened this issue Jun 22, 2023 · 1 comment
Closed

Allow using a single env template for multiple outputs #351

Zeko369 opened this issue Jun 22, 2023 · 1 comment

Comments

@Zeko369
Copy link

Zeko369 commented Jun 22, 2023

We're doing a multi-tenant SaaS where we deploy multiple environments per customer so we'd like to have a .env.[stage|production].erb that's used to generate all tenant envs i.e. .env.stage-microsoft or .env.production-google (instead of having 2 * number of tenants .env templates)

Something along the lines of bin/mrsk envify -d google -t .env.stage.erb -> .env.stage-google

Also to make this more configurable we'd use <%= ENV['MRSK_DESTINATION'] %> inside of the template to differentiate between destinations

@djmb
Copy link
Collaborator

djmb commented Sep 30, 2024

We've removed kamal envify in Kamal 2

@djmb djmb closed this as completed Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants