SoloLVL

Proven solution: do not start supervisor like but as Reference

UPD: php is started via supervisor. If I stop that via supervisor and start in the same way, but manually via shell -- then I am able to get env vars.

I like your idea about putting them into config file during deployment, thanks! Regarding .env file -- I use Laravel and obviously use that .env file for vars & secrets, but I use aws-php-sdk, which uses getenv() function to get aws creds from env vars of the pod. I also cache configs, so .env file no more readable after caching, that's why I am so worried about the fact I cannot access system level env vars. But the most weird point is that other Laravel & Symfony apps of the friend of mine with the same configs have access to system lvl env vars. Appreciate your time and help!

Thanks! The env vars I need are sensitive, so I just cannot set them in plaintext within config files of the server

Problem: php-fpm unable to access env vars via getenv() func, meanwhile php-cli can Circumstances: -- php version 8.1.10 -- clear_env is set to no in /etc/php/8.1/fpm/pool.d/www.conf -- vars are set, thus is it possible to see them via shell env command or via php-cli with getenv() -- using ubuntu22 -- php-fpm runs under user which has access to those env vars Open to any thought, ready to provide more details