You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today I realized that there's really no reason for .okta.env to have export or use quotes around values. If we remove export and the quotes from the values, running source .okta.env will still set the environment variables.
I'm not sure if this will work on Windows. However, if it does, I think we should switch to it and update old blog posts. With the CLI include, it should be easy.
One of the nice things about moving to a syntax recognized by dotenv is you can copy/paste into your IDE for environment variables and you can also rename it to .env and it'll set the variables for Docker Compose.
The text was updated successfully, but these errors were encountered:
Today I realized that there's really no reason for
.okta.env
to have export or use quotes around values. If we removeexport
and the quotes from the values, runningsource .okta.env
will still set the environment variables.I'm not sure if this will work on Windows. However, if it does, I think we should switch to it and update old blog posts. With the CLI include, it should be easy.
One of the nice things about moving to a syntax recognized by
dotenv
is you can copy/paste into your IDE for environment variables and you can also rename it to.env
and it'll set the variables for Docker Compose.The text was updated successfully, but these errors were encountered: