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
In production, the .env files are also parsed and loaded on each request. So the easiest way to define env vars is by deploying a .env.local file to your production server(s) with your production values.
To improve performance, you can optionally run the dump-env command (available in Symfony Flex 1.2 or later):
uhm sorry. remembered (and re-read) this ticket wrong. It is not implemented of course.
I have no immediate plans in creating this feature, especially because I don't have a need for it. So if someone wants to go ahead an create a PR, I'll happily review it. @dogawaf Want to give this one a shot?
Actually, it is kind of implemented. You can implement your own adapter, that does make use of a cache file that is either generated on the fly or on build time. So this code can be shared in a Gist. Or a PR can be created here for yet another adapter...
garfieldius
added a commit
to garfieldius/dotenv-connector
that referenced
this issue
Jan 20, 2025
Hi Helmut
First of all, thx for sharing again awesome code with TYPO3 community. It is very valuable.
Using symfony framework (and symfon/flex), I see performance benefits on production system with the help of symfony:dump-env command.
Quoting the symfony doc:
Would it be possible that helhum/dotenv-connector also ships this functionality in order to make TYPO3+dotenv even faster?
The source code of the command in symfony/flex: https://github.com/symfony/flex/blob/master/src/Command/DumpEnvCommand.php
Cheers.
The text was updated successfully, but these errors were encountered: