fix(sirius-press): stop writing dead build args into the installer's .env

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.
This commit is contained in:
Silent Mode 2026-09-21 03:24:24 +02:00
parent a65556726e
commit 05d77a0187

View file

@ -81,8 +81,9 @@ if [ -f .env ]; then
say "keeping the existing .env" say "keeping the existing .env"
else else
say "writing .env with generated passwords" say "writing .env with generated passwords"
# shellcheck source=tools/wordpress.lock # No WordPress version or checksum here: core is vendored in the
source "$DIR/tools/wordpress.lock" # 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 "# Written by install.sh on $(date -u +%Y-%m-%dT%H:%M:%SZ)."
echo "DB_NAME=wordpress" echo "DB_NAME=wordpress"
@ -93,9 +94,6 @@ else
echo "HTTP_PORT=$PORT" echo "HTTP_PORT=$PORT"
echo "WP_DEBUG=false" echo "WP_DEBUG=false"
echo "SIRIUS_PRESS_KEY=$(random)" echo "SIRIUS_PRESS_KEY=$(random)"
echo "WP_VERSION=$WP_VERSION"
echo "WP_URL=$WP_URL"
echo "WP_SHA256=$WP_SHA256"
} > .env } > .env
chmod 600 .env chmod 600 .env
fi fi