fix: something
This commit is contained in:
@@ -159,8 +159,12 @@ source-gamepanel/
|
||||
| Rust | `didstopia/rust-server` | 28015 | — | — |
|
||||
| Satisfactory | `wolveix/satisfactory-server` | 7777 + 8888/tcp | — | — |
|
||||
| FiveM | `spritsail/fivem:stable` | 30120 | `server.cfg` (keyvalue-style) | — |
|
||||
| ARK: Survival Evolved | `hermsi/ark-server` | 7777/udp + 7778/udp + 27015/udp + 27020/tcp | `GameUserSettings.ini`, `Game.ini` | — |
|
||||
|
||||
Many games can be added with a database seed entry alone. Some images still need small daemon-side tweaks for mount paths, port protocols, or config parsing.
|
||||
Most games only need a database seed entry: the container mount point, the
|
||||
in-game stop command and the shutdown budget are all columns on `games`, so no
|
||||
daemon change is required for a new image. Games whose process ignores stdin
|
||||
(Source engine, ARK) get their console commands over RCON automatically.
|
||||
|
||||
---
|
||||
|
||||
@@ -258,19 +262,23 @@ Open `http://localhost:5173` — login with `admin@gamepanel.local` / `admin123`
|
||||
## Production Deployment
|
||||
|
||||
```bash
|
||||
# Configure environment
|
||||
cp .env.example .env
|
||||
# Edit .env with production values (strong JWT secrets, real DB passwords)
|
||||
git clone https://github.com/your-org/source-gamepanel.git
|
||||
cd source-gamepanel
|
||||
|
||||
# Deploy full stack
|
||||
# Generates .env with fresh secrets + daemon-config.yml, creates data dirs
|
||||
./scripts/install.sh
|
||||
|
||||
# Builds and starts everything; schema migration and seeding run automatically
|
||||
docker compose up -d --build
|
||||
|
||||
# Run migrations inside the API container
|
||||
docker compose exec api node -e "..."
|
||||
# Or connect to the DB directly and run drizzle-kit migrate
|
||||
```
|
||||
|
||||
The web service is exposed on port 80 with nginx handling SPA routing and API proxying.
|
||||
Open `http://<server-ip>` and sign in with `admin@gamepanel.local` / `admin123`.
|
||||
|
||||
The panel serves plain HTTP on `WEB_PORT` (default 80) and does **not** manage
|
||||
TLS or domains — put your own reverse proxy in front of it and set
|
||||
`CORS_ORIGIN` to the origin users actually open. See
|
||||
[INSTALLATION.md](INSTALLATION.md#26-tls-domain-and-reverse-proxy) for Caddy and
|
||||
nginx examples.
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user