caleb-brown/temper
1
0
Fork 0
Code Issues 36 Pull requests Projects Releases Packages Wiki Activity Actions

Boot a secure Temper Deployment #9

New issue
Open
opened 2026-07-14 22:32:16 -04:00 by caleb-brown · 0 comments
caleb-brown commented 2026-07-14 22:32:16 -04:00
Owner
Copy link

What to build

A Temper Operator can start a fresh Docker Compose deployment, apply its schema explicitly, bootstrap the first Operator, sign in, and see that the service is ready.

Acceptance criteria

  • A fresh documented Compose startup brings up PostgreSQL plus separate stateless web and worker processes.
  • Schema migration is an explicit operation; application startup never creates or mutates schema implicitly.
  • The first Temper Operator can be bootstrapped exactly once without enabling public signup.
  • Local authentication uses a strong password hash, secure session defaults, logout, and a protected Operator landing page.
  • Liveness reports process health, while readiness reports database reachability and schema compatibility.
  • An external-behavior test proves fresh startup, bootstrap, login, protected access, and logout against real PostgreSQL.

Blocked by

  • #44 — Specify v1 acceptance scenarios and implementation slices
## What to build A Temper Operator can start a fresh Docker Compose deployment, apply its schema explicitly, bootstrap the first Operator, sign in, and see that the service is ready. ## Acceptance criteria - [ ] A fresh documented Compose startup brings up PostgreSQL plus separate stateless web and worker processes. - [ ] Schema migration is an explicit operation; application startup never creates or mutates schema implicitly. - [ ] The first Temper Operator can be bootstrapped exactly once without enabling public signup. - [ ] Local authentication uses a strong password hash, secure session defaults, logout, and a protected Operator landing page. - [ ] Liveness reports process health, while readiness reports database reachability and schema compatibility. - [ ] An external-behavior test proves fresh startup, bootstrap, login, protected access, and logout against real PostgreSQL. ## Blocked by - [#44](https://git.caleb-brown.dev/caleb-brown/temper/issues/44) — Specify v1 acceptance scenarios and implementation slices
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
dev
t3code/hygiene-review
t3code/configurable-llm-timeout
fix/openai-non-streaming-completions
t3code/test-incorrect-changes
No results found.
Labels
Clear labels   
ready-for-agent
Fully specified and ready for an implementation agent

  
wayfinder:grilling
Human-in-the-loop product or domain decision

  
wayfinder:map
Canonical Wayfinder map

  
wayfinder:prototype
Human-in-the-loop concrete prototype

  
wayfinder:research
Agent-driven primary-source research

  
wayfinder:task
Task that unblocks a Wayfinder decision

No labels
ready-for-agent
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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.

Blocks
#10 Configure and verify the model provider
caleb-brown/temper
#11 Connect and verify a Forgejo service identity
caleb-brown/temper
#13 Activate a repository Review Policy
caleb-brown/temper
#22 Manage Temper Operators and sessions
caleb-brown/temper
Depends on
#44 Specify v1 acceptance scenarios and implementation slices
caleb-brown/temper
Reference
caleb-brown/temper#9
No description provided.