Decisions
Add Decision
Records
Chad's Tools OS is the parent platform and application portal. apps.chadmgagnon.com is the portal/app launcher and should eventually own login, user preferences, and app access.
ServerAdmin is the single server administration console. adm.chadmgagnon.com is for managing the server, infrastructure records, users, apps, services, logs, backups, deployments, security, themes, and managed nodes.
InfoKeeper is a dev/staging-only project memory tool. It should not be installed on production servers. Production servers should focus on CTOS, ServerAdmin, and production apps.
Standalone InfraKeeper should be absorbed into ServerAdmin over time. Infrastructure inventory, domains, DNS, ports, routes, services, and nodes belong in ServerAdmin.
Development ServerAdmin is the workshop for building, testing, InfoKeeper, and release packaging. Production ServerAdmin is the locked-down console for monitoring, deployments, backups, security, and recovery.
Dev should build release packages. Production should accept uploaded release packages, validate them, back up, deploy, verify, and roll back if needed. Dev should not directly modify production.
CTOS and ServerAdmin must share login across apps.chadmgagnon.com and adm.chadmgagnon.com using a shared .chadmgagnon.com session cookie.
Remote nodes behind firewalls, such as the ADS-B receiver, must phone home outbound to ServerAdmin. ServerAdmin queues approved commands; the node polls, executes only allowlisted commands locally, and reports results back.
Do not expose raw shell command execution through ServerAdmin. ADS-B controls must use an approved-command queue and an allowlisted node agent.
ServerAdmin navigation should use clear conventional names and dropdown categories: Manage, Infrastructure, Operations, and System. Avoid vague one-word labels where possible.
The platform is called Chad's Tools OS. apps.chadmgagnon.com is the OS/home portal/app launcher.
adm.chadmgagnon.com is ServerAdmin only. ServerAdmin is a default installed app/control panel, not the parent platform.
Users only see apps enabled for them. User edit pages control app access with simple on/off checkboxes.
No app grouping yet and no complex permission levels yet. App access is currently on/off.
Long-term auth model is shared login/SSO: log into the app portal once, then direct app URLs authenticate from that prior login and return to the requested app.
InfoKeeper should remain a separate app under Chad's Tools OS and serve as project memory/session continuity, not be merged into ServerAdmin.
InfraKeeper should remain a separate app under Chad's Tools OS and serve as infrastructure inventory, while ServerAdmin manages and summarizes it.