Skip to content

12 Administration and Operations

This chapter is your day-2 operator runbook for Athene. Use it to keep package indexing reliable, logs actionable, and licensing state healthy over time.

12.1 Prerequisites

  • Admin access to Athene.
  • Access to mounted workspace, config, and logs directories.
  • A place to record operational checks (ticket, runbook, or audit note).
  • A known-good import/sync workflow from 10 Sync, Export, and Distribution.

12.2 Quick Start

Day-1 validation pass

  1. Confirm API and CLI reachability.
  2. Import one known package.
  3. Confirm package appears in list-packages.
  4. Run one sync/export test.
  5. Confirm logs are written under configured log root.

Day-30 recurring maintenance pass

  1. Review error patterns in application logs.
  2. Validate activation state files exist and are readable.
  3. Verify upload limits still match artifact sizes.
  4. Run controlled reindex only if index drift is suspected.
  5. Record actions and outcomes.

Useful operator commands

athene reindex
athene debian list-packages
athene ls /r

12.3 Key Parameters Explained

  • ATHENE_LOGS_ROOT: where runtime logs are stored.
  • ENABLE_CONSOLE_LOG: controls whether logs are emitted to container stdout.
  • ATHENE_MAX_FILE_SIZE / ATHENE_MAX_REQUEST_SIZE: import reliability boundaries.
  • ATHENE_CONFIG_ROOT: location containing activation and config files.
  • license-agreement.json and license.jwt: local activation state files under config root.

Tip

Reindex is a recovery tool, not a normal workflow. If you need it frequently, investigate import quality, naming consistency, and storage health instead of treating reindex as routine maintenance.

12.4 Backup and Recovery Scope

At minimum, back up:

  • Workspace data (repository content and metadata)
  • Config files (auth/access settings)
  • License state files under config root

Test restore in a non-production environment before relying on backups for incident recovery.

Next chapter: 13 Integrations.