651a35d4be
Phase 2 references for the host-agent Dune adapter, moved out of volatile /tmp
into docs/reference-repos/ (per Commander). Three upstream projects, .git +
node_modules + compiled binaries stripped (16MB source). Nested AI-instruction
files (.claude/, CLAUDE.md) removed so they don't pollute Corrosion sessions.
- icehunter/ dune-admin (Go+React) — 4 control planes; SETUP_DOCKER.md is the
closest analog to our agent's Dune docker control plane (compose
lifecycle, docker logs, RabbitMQ-via-exec, dune Postgres schema)
- adainrivers/ Rust/Tauri desktop — SSH+k8s BattleGroup control, maintenance
daemon, in-game admin console (Rust idiom reference)
- the4rchangel/ Node web UI replacing battlegroup.bat — matches the Commander's
Hyper-V self-host path + game-config schema
See docs/reference-repos/README.md for the full index + how we use each.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
60 lines
2.8 KiB
Markdown
60 lines
2.8 KiB
Markdown
# Dune Dedicated Server Manager
|
|
|
|
A desktop manager for existing Dune Awakening dedicated servers.
|
|
|
|
|
|
|
|
The app manages already-provisioned Dune dedicated servers over SSH and
|
|
Kubernetes control commands. It does not install the game server, create VMs,
|
|
configure Hyper-V, provision Ubuntu, or manage external tools such as SteamCMD.
|
|
|
|
## Features
|
|
|
|
- Remote server profile management with SSH private-key authentication
|
|
- BattleGroup status, start, stop, restart, and update controls
|
|
- Component diagnostics, log viewing, and safe restart actions
|
|
- Secure Director, File Browser, PostgreSQL, and PgHero access through local SSH tunnels
|
|
- Bundled `dune-server-service` daemon for on-host scheduled maintenance (daily restarts with in-game warnings, automated backups, server update check + apply) — installed over SSH straight from the Management card
|
|
- Admin console for in-game actions: item grants, vehicle spawns, skill/journey/XP tags, player lookup with live pawn location, and a logged history of every published command
|
|
- Automated tasks tab with editable schedule settings (daily restart time, warning lead/frequency, update apply lead, IANA timezone) — saving auto-restarts the service so changes apply immediately
|
|
- Welcome Package automation: a per-player onboarding chain (item grants, water refill, welcome whisper) driven by Postgres player detection, tracked in the management service's SQLite ledger, and configurable from the Welcome Package tab with both a visual editor and a raw JSON mode
|
|
|
|
|
|
|
|
More management features coming soon.
|
|
|
|
## Install
|
|
|
|
Download the latest release for your operating system from GitHub Releases.
|
|
|
|
- Windows: run the NSIS installer.
|
|
- Linux: use the AppImage or Debian package.
|
|
- macOS: use the DMG for your Mac architecture.
|
|
|
|
After launching the app, add an existing server profile with its host, SSH user,
|
|
and private key path, then refresh it to detect BattleGroups and management
|
|
endpoints.
|
|
|
|
## Managed Server Assumptions
|
|
|
|
The target server must already be installed and reachable over SSH. The app
|
|
expects the Dune Kubernetes resources and vendor management scripts to exist on
|
|
the server before you add it.
|
|
|
|
Required player-facing/server ports depend on your own server deployment. A
|
|
typical dedicated-server deployment uses:
|
|
|
|
- UDP 7777-7810 for game servers
|
|
- TCP 31982 for RMQ
|
|
|
|
If you found a bug or are having other issues, please create an issue here:
|
|
https://github.com/adainrivers/dune-dedicated-server-manager/issues
|
|
|
|
## Building From Source
|
|
|
|
See [Building From Source](docs/building-from-source.md).
|
|
|
|
## License
|
|
|
|
MIT License. See [LICENSE](LICENSE).
|