DASH v0.1.0-beta.1

DASH v0.1.0-beta.1

This is the first packaged DuneAwakeningSelfHost release. It is a complete
Linux x86_64/AVX2 operations and administration package for the official
Dune: Awakening Self-Hosted Server stack.

The beta label reflects third-party clean-host installation coverage, not a
known incomplete feature-parity row. The current audited peer catalogue is
36/36 current with no remaining feasible Partial or Build rows.

Highlights

• Configurable minimum-footprint, adaptive balanced-retention, full-warm, and
  custom map lifecycle policies covering all official partitions.
• Private Admin dashboard with service operations, logs, backups, restore
  drills, readiness, governance, players, economy, community, modding, and
  discovery surfaces.
• Native offline life recovery, native offline teleport, safe in-game
  &teleport, and native character transfer backup/restore with backup-first
  guarded execution and isolated rollback proofs.
• Four-eyes approval, exact change contracts, tamper-evident mutation flight
  recorder, desired-state attestation, deployment assurance, SLOs, alerts, and
  signed operator briefing.
• Automated backups, disposable PostgreSQL and RabbitMQ recovery drills,
  optional streaming replica/offsite sync, and fenced active/passive HA.
• Ansible, Proxmox, cloud-init, Pelican/Pterodactyl, systemd, public-site, and
  Discord/community deployment surfaces.
• Deterministic source package, SPDX 2.3 SBOM, SHA-256 manifest, in-toto/SLSA
  provenance, GitHub artifact attestations, and immutable release publication.

Assets

Use dash-v0.1.0-beta.1-linux-x86_64.tar.gz for the supported server install.
The Linux server, Linux client, and Windows client loader packages are
experimental research/modding artifacts and remain separately gated.

Download SHA256SUMS and verify the selected asset before installation. The
GitHub release itself and its assets can also be verified with:

gh release verify v0.1.0-beta.1 \
  --repo snapetech/DuneAwakeningSelfHost
gh attestation verify dash-v0.1.0-beta.1-linux-x86_64.tar.gz \
  --repo snapetech/DuneAwakeningSelfHost

Installation

tag=v0.1.0-beta.1
repo=https://github.com/snapetech/DuneAwakeningSelfHost
asset="dash-${tag}-linux-x86_64.tar.gz"

curl -fL "$repo/releases/download/$tag/$asset" -o "/tmp/$asset"
curl -fL "$repo/releases/download/$tag/SHA256SUMS" -o /tmp/SHA256SUMS
(cd /tmp && grep "  $asset\$" SHA256SUMS | sha256sum -c -)

tar -xOf "/tmp/$asset" \
  "dash-${tag}-linux-x86_64/scripts/install-release.sh" \
  > /tmp/dash-install-release.sh
chmod 0755 /tmp/dash-install-release.sh

ref="$(curl -fsSL "https://api.github.com/repos/snapetech/DuneAwakeningSelfHost/git/ref/tags/$tag" |
  jq -r '.object.sha')"
sudo /tmp/dash-install-release.sh install \
  --ref "$ref" \
  --sha256 "$(sha256sum "/tmp/$asset" | awk '{print $1}')" \
  --archive "/tmp/$asset" \
  --activate

Installation and activation do not start or restart any service. Runtime state
and operator configuration persist under /var/lib/dash; immutable source
releases live under /opt/dash/releases.

After installation, create/review the private .env, obtain the entitled
official Steam package, run scripts/load-images.sh, execute the bootstrap
checklist, initialize the database once, and start the selected map policy.

Platform support

• Supported server: Linux x86_64 with AVX2 and Docker Compose.
• Automated provisioning: Ubuntu/Debian and Proxmox Linux guests.
• Manual Linux hosts: Fedora/RHEL/Arch-family systems.
• Operator workstations: Windows, macOS, and Linux over SSH.
• Not native server targets: Windows, macOS, or ARM64.
• Best effort: Podman.

Not included

This release does not contain or download Funcom binaries, Steam package files,
container images, game assets, credentials, saves, databases, backups, captures,
TLS material, or logs. Operators must obtain the official server package using
an entitled Steam account.

Upgrade and rollback

The first release has no prior packaged version to upgrade from. Existing Git
checkouts can install it without touching running services, migrate their
private state/configuration deliberately, and schedule a guarded restart.

Rollback swaps the immutable current and previous symlinks and also leaves
services untouched. See docs/releases.md and docs/deployment-packaging.md.