4 ms·
Nice work! This looks very promising. The only thing I would add is the difference in packages seems a bit weird: - Five seems low for projects in the first ti
by aliasxneo 3y ago
Nice work! This looks very promising. The only thing I would add is the difference in packages seems a bit weird:
- Five seems low for projects in the first tier
- Projects are unlimited in the second tier, but environments are not? Is that a technical limitation?
- vmatsiiako 3y agoThanks for sharing this! No, this is not a technical limitation. These are just the usage numbers that we saw from our users – in other words, it is very rare that teams need to have over 10 environments. What is your use case for having more then 10 environments per project?
- booi 3y agoIf you need more than 10, it's usually because it's 1 environment per developer or 1 environment per branch
- vmatsiiako 3y agoFor the use case of having 1 env per developer: you can use our secret override feature which allows users to branch out from "env_X" with their own secret values For the use case of having each environment per branch: yes, you would need to have more than 10 environments