2 ms·
Isn't it just environment variables but rather then setting it manually it's in a file? So the spec is the same as regular environment variables?
by dubcanada 3y ago
Isn't it just environment variables but rather then setting it manually it's in a file?
So the spec is the same as regular environment variables?
- SOLAR_FIELDS 3y agoNo, python_dotenv allows some rudimentary templating in the .env file. So it’s not just specifying env vars
- dubcanada 3y agoThat's silly, but I don't think that's solved by a spec. Even with specs there is still JSON-LD, JSON 2.0, JSON API, etc.
- SahAssar 3y agoNitpick: JSON 2.0 is not a thing. JSON is versionless, maybe you are thinking of JSON5 (which is not a version, it's a superset of JSON with ECMAscript 5 features) or JSONC (also not a version, also a superset of JSON, but this time with comments). JSON-LD and JSON-API are both specs for the contents of JSON, not the dataformat itself.
- panzi 3y agoDifferent dotenv implementations disagree on weather quoting is possible (with quoting comes multi line support). There is more opportunity for disagreement, like weather comments are supported or empty lines are ignored. But all that I used support comments and empty lines (though not all of them support quoted values).
- Too 3y agoThere is no such thing as a spec for setting “regular” environment variables. Well there is but that’s a much deeper concept in Linux, than what most people get exposed to, in the execve family of functions, where it is defined in C as an array of strings with the key separated from value only by =. Unless you refer to how to do it in shell. That wouldn’t be applicable to a configuration language. Shell has a lot richer syntax and more complex logic, allowing variable templating and even running processes inside a string definition using $(). All the quoting rules around that must be different.