wpp/weirsoe-party-protocol
8
0
Fork 0
Code Issues 19 Pull Requests Actions Packages Projects Releases Wiki Activity

fix(staging): ensure wpp can write sqlite db during deploy
All checks were successful
CI / test-and-quality (push) Successful in 1m31s
Details
CI / test-and-quality (pull_request) Successful in 1m34s
Details

Browse Source
This commit is contained in:
Asger Geel Weirsøe
2026-02-28 11:20:54 +00:00
parent 850a364251
commit 173df0fd6f
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
infra/staging/deploy_staging.sh
View File

@@ -17,6 +17,11 @@ rm -rf src && mkdir src
tar -xzf app.tar.gz -C src --strip-components=1 tar -xzf app.tar.gz -C src --strip-components=1
rm -rf /opt/wpp-staging/app/* rm -rf /opt/wpp-staging/app/*
cp -a src/. /opt/wpp-staging/app/ cp -a src/. /opt/wpp-staging/app/
# Ensure deploy artifact copied as root does not leave SQLite/app tree non-writable for wpp.
chown -R wpp:wpp /opt/wpp-staging/app
if [ -f /opt/wpp-staging/app/db.sqlite3 ]; then
chmod 664 /opt/wpp-staging/app/db.sqlite3
fi
cd /opt/wpp-staging/app cd /opt/wpp-staging/app
runuser -u wpp -- python3 -m venv .venv runuser -u wpp -- python3 -m venv .venv
runuser -u wpp -- .venv/bin/pip install -U pip >/dev/null runuser -u wpp -- .venv/bin/pip install -U pip >/dev/null