Add Debian deployment, MariaDB storage and randomized proxy routing
This commit is contained in:
@@ -0,0 +1,35 @@
|
||||
#!/bin/bash
|
||||
# Run as root after installing the two virtual environments and private MySQL config.
|
||||
set -euo pipefail
|
||||
root=/opt/kaoyan-studio-deploy
|
||||
test -f "$root/mysql.json"
|
||||
test -x "$root/venv/bin/python"
|
||||
test -x "$root/proxy-venv/bin/python"
|
||||
id kaoyan >/dev/null 2>&1 || useradd --system --user-group --home-dir /var/lib/kaoyan-studio --shell /usr/sbin/nologin kaoyan
|
||||
install -d -m 700 -o kaoyan -g kaoyan /var/lib/kaoyan-studio
|
||||
install -d -m 750 -o kaoyan -g kaoyan "$root/proxy_pool/log"
|
||||
chown root:kaoyan "$root/mysql.json"
|
||||
chmod 640 "$root/mysql.json"
|
||||
install -m 640 -o root -g kaoyan "$root/app/deploy/kaoyan-studio.env.example" /etc/kaoyan-studio.env
|
||||
for unit in kaoyan-studio kaoyan-proxy-api kaoyan-proxy-scheduler; do
|
||||
install -m 644 "$root/app/deploy/$unit.service" "/etc/systemd/system/$unit.service"
|
||||
done
|
||||
visudo -cf "$root/app/deploy/kaoyan-pool-sudoers"
|
||||
install -m 440 "$root/app/deploy/kaoyan-pool-sudoers" /etc/sudoers.d/kaoyan-pool
|
||||
if ! docker container inspect kaoyan-proxy-redis >/dev/null 2>&1; then
|
||||
docker run -d --name kaoyan-proxy-redis --restart unless-stopped \
|
||||
-p 127.0.0.1:6381:6379 -v kaoyan-proxy-redis:/data \
|
||||
redis:7.2 redis-server --appendonly yes
|
||||
fi
|
||||
python3 - <<'PY'
|
||||
from pathlib import Path
|
||||
path = Path('/opt/kaoyan-studio-deploy/proxy_pool/setting.py')
|
||||
text = path.read_text()
|
||||
text = text.replace('HOST = "0.0.0.0"', 'HOST = "127.0.0.1"')
|
||||
text = text.replace("DB_CONN = 'redis://:pwdstring@127.0.0.1:6379/0'", "DB_CONN = 'redis://127.0.0.1:6381/0'")
|
||||
path.write_text(text)
|
||||
PY
|
||||
systemctl daemon-reload
|
||||
systemctl enable kaoyan-studio kaoyan-proxy-api kaoyan-proxy-scheduler
|
||||
systemctl start kaoyan-proxy-api kaoyan-proxy-scheduler
|
||||
# The workbench starts only after its database/credential migration is validated.
|
||||
Reference in New Issue
Block a user