mirror of
https://github.com/Corfirean/coa-server-manager.git
synced 2026-11-19 03:25:56 +00:00
docker::install is the Linux counterpart of install::install_base and shares none of its code (the Windows installer and its folder checks are untouched). Same order of events: signed manifest, folder / space / game data checks, verified download, extraction into <dest>.installing, database, one rename. Docker must be usable; a failure removes the containers, the volume and the staging folder. The databases start from the package's own dumps, Database/baseline/<kind>.sql.zst, in the format of the Manager's backups, taken in a state where every migration of the package is applied. The installer imports them, records the migrations as applied (baseline) in a few bulk statements, and creates the acore account, the realm port and the console account. Rebuilding from the repository's SQL does not work: pending migrations such as rev_20260903_01_live_class_baseline are guards generated from the maintainers' live database and refuse to run on a database built from the base scripts, whatever the order. - coa-release export-baseline --server DIR --out DIR produces the dumps from a prepared server (repack or Docker). - The game data stays where the person has it (dataDir in docker.json, mounted read-only), checked at install time. - ensure_main_configs creates worldserver.conf / authserver.conf from their .dist templates when missing, at install and at every start, never overwriting. - Fix (affects the backend merged in 0.6.0): the database container's health check is now a ping over TCP. On a new volume the image first runs a temporary server that answers on its socket but takes no network connection, so the container was healthy about four seconds (10 s against 14 s measured) before TCP worked. - docs/ARCHITECTURE.md: D13 (installation, package contract) and D14 (how Windows and Linux code are kept apart). Tested: 12 new tests (folder rules, settings, package checks, bulk ledger SQL, failure cleanup with an in-memory docker), and real runs of the whole chain through examples/docker_install: baseline dumps exported from a prepared server, package signed with a throwaway key, installed in 171 s, started by the Manager (database healthy, world ready in 8 s, auth up), console reached with the account the installer created, 1630 migrations recorded as applied.
22 lines
1.2 KiB
Rust
22 lines
1.2 KiB
Rust
//! Install a new Docker server from a package folder, for a manual end-to-end check on Linux (needs docker).
|
|
//! usage: docker_install <package folder> <destination> <game data folder> <public key (base64)>
|
|
//! The key is the one the package was signed with (the production key is only used by the Manager itself).
|
|
use coa_core::docker::install::{install, Params};
|
|
use coa_core::download::Cancel;
|
|
use coa_core::install::Source;
|
|
use coa_core::registry::Registry;
|
|
use std::path::PathBuf;
|
|
|
|
fn main() {
|
|
let a: Vec<String> = std::env::args().skip(1).collect();
|
|
assert!(a.len() == 4, "usage: docker_install <package folder> <destination> <game data folder> <public key>");
|
|
let registry = Registry::at(std::env::temp_dir().join("coa-docker-install/installs.json"));
|
|
let t = std::time::Instant::now();
|
|
let done = install(
|
|
&Params { source: Source::Dir(PathBuf::from(&a[0])), dest: PathBuf::from(&a[1]), data_dir: PathBuf::from(&a[2]), trusted_key: &a[3], registry: ®istry, cancel: Cancel::default() },
|
|
&|s| eprintln!(" {:>3}% {} {}", s.percent, s.step, s.detail.unwrap_or_default()),
|
|
)
|
|
.unwrap_or_else(|e| panic!("install failed: {e}"));
|
|
println!("installed {} at {} in {:?}", done.version, done.path, t.elapsed());
|
|
}
|