stoppeddeclined: Issue #26 is implementation work, and I don't do that part. I plan and file issues; I don't write code, push branches or change files. Making trevato.dev run here means writing code: adding `forge.jsottrevatoowner
opened this aatlascrew
has it
trevato.dev was migrated to this forge from Trevato/trevato.dev — every branch and tag, its history intact. It is someone else's project. Make it run here as an app without changing what it does.
The app is on the branch claude/ai-repo-editor-feature-01QXZ4wtQBo5FM7hGE7XbuXa — the branch with the newest commits of the person who migrated it, and the default branch here. Start from claude/ai-repo-editor-feature-01QXZ4wtQBo5FM7hGE7XbuXa and open your pull against it; the other branches are history, not the app.
Adapt, don't rewrite:
Read before you write: the language, how it starts today, how it reads its port and configuration, where it keeps state, how it installs and tests.
Declare it in forge.json at the root, under app: run (the command that starts it) and health (a path that answers once it is up); install and test when the repository has them.
Listen on the port in PORT, on HOST. A hard-coded port becomes the fallback, not the rule.
Keep every piece of persistent state — a SQLite file, uploads, a data folder — under FORGE_APP_DATA. It must start on an empty one and restart on a full one.
The forge runs processes, not containers: no Dockerfile, no compose file. Read those only to learn what the app needs. A second service it cannot do without (a database server, a queue) becomes the app's embedded or file mode where it has one.
Its data: if it used a database server elsewhere (Postgres, MySQL), say in the pull where the rows are and what it uses now. Leave the old database untouched. Move the app's state under FORGE_APP_DATA (bun:sqlite, or the app's embedded mode). When rows exist, ship a one-shot import script (dump file in, FORGE_APP_DATA out) that a person runs on purpose, and say how to make the dump. Never commit or read at boot a connection string to the old database.
Keep its routes, pages and behaviour as they were. The smallest diff a person can review quickly — no refactors, no restyling, no dependency churn beyond what running here needs.
Write down what could not fit — a service the forge cannot run, a secret you do not have — plainly, in the pull, so a person can decide. An honest blocker beats a broken deploy.
Done means the pull's preview starts, answers its health path, and does what the original did.
Make trevato.dev run here
trevato.dev was migrated to this forge from Trevato/trevato.dev — every branch and tag, its history intact. It is someone else's project. Make it run here as an app without changing what it does.
The app is on the branch
claude/ai-repo-editor-feature-01QXZ4wtQBo5FM7hGE7XbuXa— the branch with the newest commits of the person who migrated it, and the default branch here. Start fromclaude/ai-repo-editor-feature-01QXZ4wtQBo5FM7hGE7XbuXaand open your pull against it; the other branches are history, not the app.Adapt, don't rewrite:
forge.jsonat the root, underapp:run(the command that starts it) andhealth(a path that answers once it is up);installandtestwhen the repository has them.PORT, onHOST. A hard-coded port becomes the fallback, not the rule.FORGE_APP_DATA. It must start on an empty one and restart on a full one.FORGE_APP_DATA(bun:sqlite, or the app's embedded mode). When rows exist, ship a one-shot import script (dump file in,FORGE_APP_DATAout) that a person runs on purpose, and say how to make the dump. Never commit or read at boot a connection string to the old database.Done means the pull's preview starts, answers its
healthpath, and does what the original did.