Документация и UX установки: полный production-fix по fix32

This commit is contained in:
2026-05-12 20:16:56 +05:00
parent 2ee50bfa8e
commit b3d274f89d
8 changed files with 266 additions and 6 deletions
+19
View File
@@ -53,6 +53,25 @@ scp -P 2323 dist/awg2-harness_<version>_amd64.deb root@<server-ip>:/root/
scp -P 2323 dist/SHA256SUMS root@<server-ip>:/root/
```
## Runtime config bootstrap на production
`--package` кладёт `config.example.toml` только в:
```text
/usr/share/doc/awg2-harness/repo/config.example.toml
```
Боевой `/etc/awg2-harness/config.toml` создаётся вручную после установки пакета:
```bash
apt install ./awg2-harness_<version>_amd64.deb
install -d -m 0755 /etc/awg2-harness
cp /usr/share/doc/awg2-harness/repo/config.example.toml /etc/awg2-harness/config.toml
nano /etc/awg2-harness/config.toml
```
Перед первым `apply-firewall` обязательно сверяйте `ssh_port`, `amnezia_port` и `peer_ipv4_cidr` с реальным состоянием хоста и Amnezia.
## Что скрипт намеренно не делает
- не устанавливает AmneziaVPN;
+10
View File
@@ -370,6 +370,16 @@ if command -v systemctl >/dev/null 2>&1; then
systemctl daemon-reload || true
fi
echo "AWG2 Harness installed."
echo "Runtime config is not created automatically by design."
echo "Create /etc/awg2-harness/config.toml manually before enabling services:"
echo " install -d -m 0755 /etc/awg2-harness"
echo " cp /usr/share/doc/awg2-harness/repo/config.example.toml /etc/awg2-harness/config.toml"
echo " nano /etc/awg2-harness/config.toml"
echo "Then validate and enable services:"
echo " awg2-harness --config /etc/awg2-harness/config.toml validate-config"
echo " systemctl enable --now awg2-harness.service awg2-reboot-scheduler.service"
exit 0
EOF