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
(we wrote about this in detail on Symfony Slack yesterday)
The idea is to provide a way for the user to define some vars in box.json which would then be available in the env for the PHAR when running it.
One example is needing to define APP_ENV to the read-only Symfony environment, which I solved in the autoload template which is currently required (I don't use DotEnv).
Another example would be APP_RUNTIME, enabling the PHAR runtime.
Thinking about this, I'm pretty sure these should be fixed: even if user passes APP_ENV to the PHAR, the embedded one should still be used. This means the user can't break the PHAR by passing APP_ENV=dev.
I'd like to use this to pass semi-sensitive credentials as environment variables at runtime. The existing sigil / replacement functionality can be used for this but has problems of its own, such as breaking static analysis and being somewhat unpredictable (if people accidentally use a magic string where they shouldn't).
Feature Request
(we wrote about this in detail on Symfony Slack yesterday)
The idea is to provide a way for the user to define some vars in box.json which would then be available in the env for the PHAR when running it.
One example is needing to define
APP_ENV
to the read-only Symfony environment, which I solved in the autoload template which is currently required (I don't useDotEnv
).Another example would be
APP_RUNTIME
, enabling the PHAR runtime.Dockerfile has a similar idea with the
ENV
instruction.Example usage
When the PHAR runs, it should see these values defined in the env as if they're real env vars.
The text was updated successfully, but these errors were encountered: