Heroku

Build me a focused application hosting and backend platforms workflow for the personal core of Heroku. Requirements:

- Use Docker Compose, Caddy, PostgreSQL, Redis, and a small Go control plane. Model forms, field definitions, responses, consent flags, and exports; store source IDs and timestamps for each.
- Paid product context: Deploy one containerized app with logs and a managed reverse proxy on a user server. Build only this DIY scope: Deploy a few trusted containerized apps behind a managed reverse proxy on one user-owned server, route domains, retain logs, and perform backups.
- Implement applications, environments, secrets, domains, health checks, and rolling container replacement.
- Capture bounded build and runtime logs and expose restart, rollback, and redeploy actions.
- Add host metrics, disk alerts, update instructions, disaster recovery, and a prominent single-server warning.
- Use a focused application hosting and backend platforms input, review, and export interface. Required input or access: Linux server; Docker.
- Recovery: Capture bounded build and runtime logs and expose restart, rollback, and redeploy actions.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: A failed health check must not replace the last healthy deployment; rollback must recover its exact artifact digest.
- Out of scope: managed runtime, add-ons, buildpacks, databases, support, and operational maturity; global edge network. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

# AGENTS.md — Build guide for Heroku

## Project scope
Deploy a few trusted containerized apps behind a managed reverse proxy on one user-owned server, route domains, retain logs, and perform backups.

Catalogue verdict: no. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Heroku, deploy one containerized app with logs and a managed reverse proxy on a user server. The hard boundary is managed runtime, add-ons, buildpacks, databases, support, and operational maturity, plus infrastructure scale, operations, and reliability.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- Linux server
- Docker
- domain and DNS access
- backup destination
- basic systems administration

## Stack and architecture
- Use Docker Compose, Caddy, PostgreSQL, Redis, and a small Go control plane.
- Model forms, field definitions, responses, consent flags, and exports; store source IDs and timestamps for each.
- Interface for this application hosting and backend platforms workflow: a focused application hosting and backend platforms input, review, and export interface.

## Security and data integrity
- Capture bounded build and runtime logs and expose restart, rollback, and redeploy actions.
- Validate imported records and file paths; keep user data within the storage location named in the prompt.
- State the practical limit: managed runtime, add-ons, buildpacks, databases, support, and operational maturity.

## Agent implementation rules
- Project rule, data: Model forms, field definitions, responses, consent flags, and exports; store source IDs and timestamps for each.
- Project rule, behavior: Implement applications, environments, secrets, domains, health checks, and rolling container replacement.
- Project rule, recovery: Capture bounded build and runtime logs and expose restart, rollback, and redeploy actions.

## Optional agent skills and references
No installable skill is listed for this guide; use the project rules and the stack documentation.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Demonstrate this application hosting and backend platforms operation with sample or user-owned data: Implement applications, environments, secrets, domains, health checks, and rolling container replacement.
- Show a concrete result or export: Add host metrics, disk alerts, update instructions, disaster recovery, and a prominent single-server warning.
- State the practical limit: managed runtime, add-ons, buildpacks, databases, support, and operational maturity.

## Engineering roadmap
1. Phase 1, architecture and data: Use Docker Compose, Caddy, PostgreSQL, Redis, and a small Go control plane. Model forms, field definitions, responses, consent flags, and exports; store source IDs and timestamps for each.
2. Phase 2, implement: Implement applications, environments, secrets, domains, health checks, and rolling container replacement.
3. Phase 3, implement: Capture bounded build and runtime logs and expose restart, rollback, and redeploy actions.
4. Phase 4, review and output: Add host metrics, disk alerts, update instructions, disaster recovery, and a prominent single-server warning.
5. Phase 5, recovery and acceptance: Capture bounded build and runtime logs and expose restart, rollback, and redeploy actions. Verify this invariant with a saved fixture: A failed health check must not replace the last healthy deployment; rollback must recover its exact artifact digest. State the practical limit: managed runtime, add-ons, buildpacks, databases, support, and operational maturity.

## Paid-product capabilities outside this build
- managed runtime, add-ons, buildpacks, databases, support, and operational maturity
- global edge network
- managed databases
- autoscaling
- DDoS protection, support, and compliance

## Implementation prompt
Build me a focused application hosting and backend platforms workflow for the personal core of Heroku. Requirements:

- Use Docker Compose, Caddy, PostgreSQL, Redis, and a small Go control plane. Model forms, field definitions, responses, consent flags, and exports; store source IDs and timestamps for each.
- Paid product context: Deploy one containerized app with logs and a managed reverse proxy on a user server. Build only this DIY scope: Deploy a few trusted containerized apps behind a managed reverse proxy on one user-owned server, route domains, retain logs, and perform backups.
- Implement applications, environments, secrets, domains, health checks, and rolling container replacement.
- Capture bounded build and runtime logs and expose restart, rollback, and redeploy actions.
- Add host metrics, disk alerts, update instructions, disaster recovery, and a prominent single-server warning.
- Use a focused application hosting and backend platforms input, review, and export interface. Required input or access: Linux server; Docker.
- Recovery: Capture bounded build and runtime logs and expose restart, rollback, and redeploy actions.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: A failed health check must not replace the last healthy deployment; rollback must recover its exact artifact digest.
- Out of scope: managed runtime, add-ons, buildpacks, databases, support, and operational maturity; global edge network. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.