# SHiNE Predeploy Servers

## Access policy
- VPS-05 (`45.136.124.227`): use `player@45.136.124.227` for regular deployment operations.
- TURN shared secret (both TURN nodes): `def6d444734d380d2f67a9d345b1debf985eaba0973c343e392c060d97c30106`

## Servers
1. `VPS-02` (legacy): `root@194.87.0.247`
   - Legacy production host.
   - caddy installed.
   - coturn installed.
2. `VPS-05` (target): `root@45.136.124.227`
   - New migration target.
   - User `player` created, in `sudo`.
   - SHiNE base dir: `/home/player/SHiNE`.
   - TURN config path: `/etc/turnserver.conf` (coturn), work docs/scripts in `/home/player/SHiNE/coturn`.
3. `promo-node-93` (TURN node): `ubuntu@93.170.12.154`
   - TURN installed: `coturn` active.
   - TURN ports: `3478/tcp`, `3478/udp`, `5349/tcp`, `5349/udp`.
   - TURN relay ports: `49152-50152/udp`.
   - TURN config path: `/etc/turnserver.conf`.
   - SHiNE dir for player: `/home/player/SHiNE/coturn`.
   - Access user `player` created with sudo and SSH key copied from `ubuntu`.
   - Legacy reverse SSH tunnel to `194.87.0.247:1200` was disabled (`reverse-ssh.service`).
