Hmm, sounds promising indeed!

I tried to make some playground files using those directives ( official docs ) but they seem broken.

#!defenv PORT:
- This should error if PORT env var is not defined. It does not.
- If it reads something, it reads it as a string (there is #!defenvs for that) because config complaints about the line
  port = PORT with column 8-13: number expected, while I have exported with export PORT=5080.
same goes for trydefenv

I will try and check if these are indeed bugs.

If they work as intended, your template idea should work just fine. But then again, a config file must be edited accordingly to try and check for these vars!

What would be the benefit over a separate config for each new service started?

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.