factorio: collect friend-group factorio.com handles + populate server-whitelist.json #79

Closed
opened 2026-05-23 20:54:38 +00:00 by coilysiren · 1 comment
Owner

Originally filed by @coilysiren on 2026-05-01T11:14:02Z - https://github.com/coilysiren/infrastructure/issues/81

Goal

Replace the stub server-whitelist.json with the actual friend-group factorio.com handles.

Context

The Sirens factorio server (kai-server) is running with whitelist enforcement on (--use-server-whitelist). Today the whitelist is just ["coilysiren"] because no one has shared their factorio.com handle yet.

Action

Collect handles from the channel - the people who showed interest are already in there. Drop them into:

/home/kai/Steam/steamapps/common/FactorioServer/server-whitelist.json

After updating, the server picks up the whitelist on next restart (or via /whitelist add <name> from the server console / RCON if wired).

Tracked file (canonical)

The whitelist is live-edited on kai-server, not tracked in git (single source of truth + nightly s3 backup covers durability). If we want it in git, that's a separate decision - whitelist contents leak factorio.com handles to anyone with repo read.

Done when

  • Whitelist contains every interested friend-group handle
  • Each handle has confirmed they can join (one-shot test)

Tracking from: #77

_Originally filed by @coilysiren on 2026-05-01T11:14:02Z - [https://github.com/coilysiren/infrastructure/issues/81](https://github.com/coilysiren/infrastructure/issues/81)_ ## Goal Replace the stub `server-whitelist.json` with the actual friend-group factorio.com handles. ## Context The Sirens factorio server (kai-server) is running with whitelist enforcement on (`--use-server-whitelist`). Today the whitelist is just `["coilysiren"]` because no one has shared their factorio.com handle yet. ## Action Collect handles from the channel - the people who showed interest are already in there. Drop them into: ``` /home/kai/Steam/steamapps/common/FactorioServer/server-whitelist.json ``` After updating, the server picks up the whitelist on next restart (or via `/whitelist add <name>` from the server console / RCON if wired). ## Tracked file (canonical) The whitelist is live-edited on kai-server, not tracked in git (single source of truth + nightly s3 backup covers durability). If we want it in git, that's a separate decision - whitelist contents leak factorio.com handles to anyone with repo read. ## Done when - [ ] Whitelist contains every interested friend-group handle - [ ] Each handle has confirmed they can join (one-shot test) Tracking from: #77
Author
Owner

Iceboxed in the 2026-05-29 backlog burn-down: factorio whitelist handles, blocked on friends. Reopen anytime if it becomes real.

Iceboxed in the 2026-05-29 backlog burn-down: factorio whitelist handles, blocked on friends. Reopen anytime if it becomes real.
Sign in to join this conversation.
No labels
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/infrastructure#79
No description provided.