---
name: init-local-memory
description: Gather deployment-specific context to create LOCAL.md when it is missing. Use at session start when LOCAL.md does not exist in the bnna repo.
tags: [context, setup, deploy, onboarding, local]
---

# Init Local Memory

`LOCAL.md` is missing. It holds real hostnames, IPs, and connection details for this
deployment. Ask the user for each item below, then write `LOCAL.md` using the template.

Do not proceed with deploy or migration tasks until `LOCAL.md` exists.

## Questions to Ask

1. **Service CT** — What is the hostname (or IP) of the container running bnna?
   - Expected format: `tls-<ip-dashes>.<domain>` e.g. `tls-10-11-8-205.vms.coolaj86.com`

2. **Postgres host** — What host and port is the Postgres DB on?
   - Expected format: internal IP + port 15432 e.g. `10.11.8.204:15432`
   - Database name (usually `bnna`)

3. **Proxmox clusters** — Which clusters are in use?
   - Dev cluster host + corresponding `~/.config/proxmox-sh/*.env` file
   - Prod cluster host + corresponding env file (read-only)

4. **Target node** — Which Proxmox node does the API provision to by default?
   - e.g. `pve1`

5. **Direct IP domain** — What domain does the TLS router use for IP-based hostnames?
   - e.g. `a.bnna.net`

## Template

Write the answers into `LOCAL.md` using this structure:

```markdown
# Deployment Context
...
## Dev Service CT
| Hostname | tls-... |
| Internal IP | 10.x.x.x |
...
## Postgres
| Internal URL | postgres://bnna:<pass>@10.x.x.x:15432/bnna?sslmode=disable |
...
## Proxmox Clusters
| dev | host | ~/.config/proxmox-sh/...env |
| prod | host | ~/.config/proxmox-sh/...env (read-only) |
...
```

Then add `LOCAL.md` to `.gitignore` if not already present.