Post Views: 23 1. When I encounter a bug in the production environment, after a new container is newly deployed, when the first run, the value of the environment variables feels that it is not the environment variable of the container, but null. On the second run, the value of its environment variables is correct. On the first run, the…
👨💻 Personal Brand
Wang Shiqiang | PHP & Go Technical Consultant
15+ years of backend development experience specializing in system maintenance, architecture optimization, performance tuning, and Linux administration.
Technical blogger since 2013 with 1,000+ original articles.
Available for consulting, long-term maintenance, and remote collaboration.
.env (14) 404 (13) add (17) Aliyun (19) Apache (13) Array (19) browser (14) Cache (13) CentOS (23) chrome (19) command line (13) composer (42) composer.json (22) composer install (13) composer update (14) console (16) Container (25) curl (15) database migration (16) delete (32) Docker (32) Dockerfile (15) ECS (12) environment variable (20) error (24) escape (12) Failed (13) file (16) filter (20) FORMAT (12) function (13) Git (27) GitHub (16) Gitlab (15) Go (36) Go 1.26 (12) Google AdSense (17) GraphQL (24) GraphQL API (14) Gutenberg (14) http (21) https (21) Installation (13) Interface (19) Jenkins (12) Jquery (13) json (24) Laravel (37) Laravel 6 (56) Laravel 9 (25) Lighthouse (17) Lighthouse 5 (14) Linux (17) Migrate (13) Module (17) MySQL (76) MySQL 5.7 (21) Nginx (46) Node.js (12) normalize.css (29) OKX (15) OneinStack (12) PHP (67) php.ini (24) PHP 7.1.12 (22) PHP 7.4 (26) phpmyadmin (15) PhpStorm (24) Polylang (30) postman (18) Query (17) queue (16) Rancher (24) Redis (39) Refactoring (12) require (12) response (13) RESTful (27) RESTful API (23) rules (12) setting (12) Shell (13) Shopify (19) Shopify CLI (12) SQL (24) String (15) Technical Blog (11) TortoiseGit (15) Twenty Twenty-Five (18) Ubuntu (37) update (20) VPN (16) Windows 10 (46) WireGuard (25) WordPress (78) WPCode (14) Wstunnel (12) Yii (40) Yii 2 (70) Yii 2.0 (51)
