Skip to main content

Would you like your #curl config file to accept environment variables? github.com/curl/curl/pull/1131…

tool_parsecfg: support environment variables in config files by bagder · Pull Request #11311 · curl/curl

Instances of ${name} will be replaced by the contents of the environment variable name at the time of the parsing. The name must be shorter than 128 bytes. tests documentation
GitHub
#curl
in reply to daniel:// stenberg://

Johannes
Johannes
• •
I kinda feel like `envsubst` is good enough to use as long as you can pass the resulting data from the pipe to the executable.
in reply to daniel:// stenberg://

James Brown
James Brown
• •
I've maintained an application (well, a pile of shell scripts dressed up as an application) in the past that wrote out curl config files dynamically with user content in them. Whoever maintains it now will need to make sure that there aren't ${ characters...
⇧