nimmerverse/nimmerworld.eachpath.local
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

introduce operational scaffold (conventions + 7 sub-dir stubs) Mirrors the nimmerverse.eachpath.local structure for nimmerworld-specific operational concerns. The fresh conventions/development-conventions.md inherits from the platform-wide nimmerverse conventions and only defines what's nimmerworld-specific: - Service identity: UID range 10300-10399 (gameserver/compositor/ director/gm) - Port allocation: +0100/+0200/+0300/+0400 within env-blocks - NATS subjects: under {env}.world.{domain}.{service}.{detail} - K8s namespaces: world-{env} - Deployment topology: dioscuri-as-substrate (per 2026-04-26 housekeeping clarification — old nimmersky/SkyrimNet retired; treat dioscuri empty) - Database conventions: nimmerworld_* table-prefix in shared phoebe-{env} Other 7 sub-dirs are stubs pointing at planned content + referencing platform conventions for shared patterns.

Browse Source
This commit is contained in:
David Martin
2026-04-26 08:49:28 +02:00
parent 0fa597c25b
commit 6acdeb7b37
8 changed files with 322 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
networking/README.md Normal file
View File

@@ -0,0 +1,15 @@
# Networking — Nimmerworld
Nimmerworld-specific network configuration.
Mostly inherits from platform networking. This directory exists for future-specific concerns (e.g., per-district network isolation, gameserver-to-NATS routing optimization, MTU tuning for high-frequency NPC chatter).
> **Platform networking:** [`../../nimmerverse.eachpath.local/networking/`](../../nimmerverse.eachpath.local/networking/) (MetalLB pool, VLAN allocations, etc.).
## Status
⏳ **Stub** — populate as networking-specific concerns arise during implementation.
---
**Version:** 0.1 | **Created:** 2026-04-26 | **Updated:** 2026-04-26