Commit Graph

3 Commits

Author SHA1 Message Date
lerko d5587958e8 feat: seed SSH users from UPTOP_ADMIN_KEY env and UPTOP_KEYS file
CI / test (pull_request) Successful in 2m59s
CI / lint (pull_request) Failing after 1m6s
CI / vulncheck (pull_request) Successful in 1m6s
On startup, reads SSH public keys from two sources:
- UPTOP_ADMIN_KEY env var (single key, quick setup)
- UPTOP_KEYS file path (authorized_keys format, team setup)

Keys already in the database are skipped (idempotent across restarts).
All seeded users get admin role. Username parsed from key comment.

Dockerfile already sets UPTOP_KEYS=/data/authorized_keys — Docker users
just drop their keys file in ./data/ and start the container.
2026-05-27 16:32:33 -04:00
lerko 9d12e3ecf1 chore: complete rename from go-upkeep to uptop
CI / test (pull_request) Successful in 4m26s
CI / lint (pull_request) Successful in 1m11s
- Module path: gitea.lerkolabs.com/lerko/uptop
- Binary: cmd/uptop/
- All imports updated to full module path
- Env vars: UPKEEP_* → UPTOP_*
- Prometheus metrics: upkeep_* → uptop_*
- Default DB: uptop.db
- Docker image: lerko/uptop
- All docs, compose files, CI updated

Only remaining "go-upkeep" reference is the fork attribution in README.
2026-05-24 20:20:35 -04:00
lerko 5a9b19b3e8 chore: add production docker-compose.yml
Single-container SQLite deploy for `docker compose up -d`.
2026-05-22 15:00:09 -04:00