From 05d77a0187f1a60611d2794628d278d36fac63b6 Mon Sep 17 00:00:00 2001 From: Silent Mode Date: Mon, 21 Sep 2026 03:24:24 +0200 Subject: [PATCH] fix(sirius-press): stop writing dead build args into the installer's .env MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit install.sh was still sourcing tools/wordpress.lock and copying WP_VERSION, WP_URL and WP_SHA256 into the generated .env. Nothing reads them any more — core is vendored and baked into the image — and a config file full of settings that do nothing invites someone to edit one and wonder why it had no effect. --- install.sh | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/install.sh b/install.sh index 7ff4467..358a2a6 100644 --- a/install.sh +++ b/install.sh @@ -81,8 +81,9 @@ if [ -f .env ]; then say "keeping the existing .env" else say "writing .env with generated passwords" - # shellcheck source=tools/wordpress.lock - source "$DIR/tools/wordpress.lock" + # No WordPress version or checksum here: core is vendored in the + # repository and baked into the image, so there is nothing to pin at + # deploy time. { echo "# Written by install.sh on $(date -u +%Y-%m-%dT%H:%M:%SZ)." echo "DB_NAME=wordpress" @@ -93,9 +94,6 @@ else echo "HTTP_PORT=$PORT" echo "WP_DEBUG=false" echo "SIRIUS_PRESS_KEY=$(random)" - echo "WP_VERSION=$WP_VERSION" - echo "WP_URL=$WP_URL" - echo "WP_SHA256=$WP_SHA256" } > .env chmod 600 .env fi