Is there interest in a PR to support multiple lines when a variable is delimited by quotes?
Do you have an example of why you would want to use a multiple line variable and export it to the process.env?
Private key. That's how we store it in heroku and aws.
On Mon, Jun 23, 2014 at 10:52 AM, Jacob Lowe [email protected]
wrote:
Do you have an example of why you would want to use a multiple line variable and export it to the
process.env?Reply to this email directly or view it on GitHub:
https://github.com/scottmotte/dotenv/issues/28#issuecomment-46871131
Ah I see, I actually have done that before. :smile:
I think this could be cool.
What are your thoughts @scottmotte or @maxbeatty ?
Indeed, I like this idea - particularly for RSA keys. Please go for it @randallb.
I'm interested in seeing how it would be done. Nervous our file format may start to find its limitations and a more structured format (JSON, YAML, etc.) may be needed. Good luck!
If anyone is wondering how to do this - until/if this functionality is built in. You can simply use \n newline characters
Ooh. Good to know. I just had a baby so it's going to be a bit, but I want
to make this happen.
ᐧ
On Fri, Jun 27, 2014 at 6:54 PM, Scott Motte [email protected]
wrote:
If anyone is wondering how to do this - until/if this functionality is
built in. You can simply use \n newline characters—
Reply to this email directly or view it on GitHub
https://github.com/scottmotte/dotenv/issues/28#issuecomment-47413718.
closing. use \n newlines for now.
Any update on this?
This issue was mysteriously closed - https://github.com/motdotla/dotenv/issues/196
This workaround is definitely not ideal for certs etc
https://github.com/motdotla/dotenv/blob/v4.0.0/test/.env#L10
Is there a technical impediment preventing its introduction?
Wish there was a better solution for this. The\n workaround is not great.
Another use case is SQL queries passed in via environment variables. It would be nice to be able to lay them out neatly, too.
Hi. I this is definitely needed to match Ruby's dotenv standard (https://github.com/bkeepers/dotenv#multi-line-values).
And for me, the \n workaround doesn't even work, \n is being sent as part of the value... I'm using the latest version, 7.0.0
And if you accidentally leave any actual new lines in the value of the var in the .env file, all the \n strings will get added to the resulting value.
Most helpful comment
Any update on this?
This issue was mysteriously closed - https://github.com/motdotla/dotenv/issues/196
This workaround is definitely not ideal for certs etc
https://github.com/motdotla/dotenv/blob/v4.0.0/test/.env#L10
Is there a technical impediment preventing its introduction?