remove myst.config.json generation, rely on .env for container deployments

This commit is contained in:
ZTatman 2026-04-08 14:52:11 -04:00
parent f1a4a6d18c
commit 31c3105e34
4 changed files with 4 additions and 23 deletions

View file

@ -93,7 +93,7 @@ GRANT_TOKEN_SECRET="your-secret-here"
- [x] Project renamed from Embargo to Myst
- [x] CLI scaffold (`myst init`)
- [x] Config generation (`.env`, `myst.config.json`)
- [x] Config generation (`.env`)
- [ ] Service foundation (FastAPI + PostgreSQL)
- [ ] `myst forgejo bootstrap` — verify Forgejo connectivity
- [ ] `myst doctor` — validate configuration

View file

@ -130,8 +130,7 @@ Only repo owners can create view links for their repos.
`myst init` should generate all Myst-owned deployment config needed for Phase 1:
- `.env`
- `myst.config.json`
- `.env` (environment variables for Docker/container deployment)
- any future Myst-only deployment templates, but never Forgejo provisioning files
`myst init` should provide inline guidance that:

View file

@ -208,7 +208,6 @@ The CLI is the primary way to configure and validate Myst against an existing Fo
- generate a grant token secret by default unless the operator pastes one
- generate all Myst-owned config files needed for deployment in Phase 1
- write `.env`
- write `myst.config.json`
- print manual follow-up actions for admin URL protection, app deployment, and Forgejo validation
- show links to Forgejo docs for API usage, token scopes, repo permissions, and the admin CLI
- remind operators to run `myst init` in the directory where Myst will be deployed, usually on the target VPS or server workspace
@ -285,7 +284,6 @@ Forgejo docs to link directly from CLI output:
Expected outputs from `init`:
- `.env`
- `myst.config.json`
- optional platform templates for Myst only (e.g., Docker Compose for Dokploy)
## Data Model

View file

@ -223,30 +223,14 @@ export async function initCommand(args?: string[]): Promise<void> {
publicUrl,
});
const configContent = JSON.stringify(
{
adminUrl,
forgejoBaseUrl,
forgejoBotUsername: answers.forgejoBotUsername,
publicUrl,
},
null,
2,
);
const outDir = process.cwd();
const envPath = path.join(outDir, ".env");
const configPath = path.join(outDir, "myst.config.json");
await preflightWriteTargets([envPath, configPath]);
await preflightWriteTargets([envPath]);
await writePrivateFile(envPath, envContent);
await writePrivateFile(configPath, configContent);
s.stop("Config files generated");
p.note(
[c.green(".env"), c.green("myst.config.json")].join("\n"),
c.yellow("Files written to current directory"),
);
p.note(c.green(".env"), c.yellow("File written to current directory"));
p.note(
[
`${c.bold("Public viewer URL:")} ${c.cyan(publicUrl)}`,