Administrators and operators
Administrator guides
In developmentOperate separate Alexandria and Stache services responsibly.
Service responsibilities
All products are In development. Release-specific administration controls and supported deployment combinations will be documented with approved releases.
Alexandria manages shared book intelligence and provider operations. Stache Server manages user accounts, personal libraries and reader data. Operate them as separate services with separate persistence and credentials. Do not connect them by writing directly into each other's databases.
Routine operation
- Record installed versions, service addresses and the date of configuration changes.
- Restrict administrator access to the people who need it.
- Check service startup, available storage and client connectivity after maintenance.
- Keep backups separate from the active installation and rehearse recovery on a disposable instance.
- Treat provider responses and imported files as untrusted input.
Provider operations can affect shared book records. Review uncertain matches rather than assuming similarly titled books are identical. Preserve source information when diagnosing metadata issues, and keep personal Stache data out of shared metadata corrections.
Maintenance planning
Notify readers before downtime and give mobile clients an opportunity to synchronize. Verify a backup before upgrades, storage changes or bulk imports. If maintenance fails, preserve diagnostics and avoid repeatedly applying changes to live data.
See provider development, backup and recovery, upgrades and troubleshooting. Do not publish configuration files containing credentials when seeking help.