DEV Community

loading...

Discussion on: Building a SaaS Product in Public - Update 1

Collapse
jverce profile image
Jay Vercellone

Hi! I have a few questions about your use cases:

  • Is sharing env variables only intended for development purposes? Or also during deployment?
  • Have you looked at other platforms like HashiCorp Vault?
  • How will it work? Do users pull the env variables from the service and use them locally? Or will the env variables be retrieved by the project's build system? One case that could happen is a user retrieving variables, then changing them and using those changed ones.
Collapse
ajones_codes profile image
Andrew Jones Author

Hey! Thanks for the questions.

  1. Both! I’m planning on supporting multiple environments per project.
  2. Yes. One competitor is Vercel’s CLI, which lets teams manually pull env variables, but it only supports one environment and of course requires you to use Vercel. HashiCorp Vault does have a lot of similar features, but I’m planning a simpler workflow than their CLI, and cheaper pricing, although I’ll need to figure that out once I’ve developed the service further.
  3. Plan right now is that the variables will be pulled at buildtime and/or runtime and dynamically injected in-memory, plus there will be an override system based on the traditional .env file. Proper logging and CLI output will help clear up confusion around overrides.