An empty firebreak_public_base_url only works while the person filling in
the wizard happens to be browsing the same origin Forgejo redirects back
to, so it can look fine during local setup and still be wrong in
production. It also leaves share URLs relative, since there is no
externally resolvable origin to build them from.
The setup page already derived the request's base URL to display the OAuth
callback hint, but persisted "" instead, so the field and the hint could
disagree. Pass the derived value through as the field's value and mark the
input required, dropping the hint that told users to leave it blank on
localhost.
Expose GET /links/repositories/{repo}/commits, resolving {owner}
server-side from the session's linked Forgejo identity like the sibling
branches route.
Take the ref as a query parameter instead of a path segment: branch names
contain slashes (docs/readme, feature/learn-public-links), which a single
path param cannot capture without a path converter. As a query param,
`ref` may also default to main.
Dropping the path default and declaring `repo` were both required for the
module to import: FastAPI asserts that path parameters have no defaults,
and an undeclared path param raised NameError at call time.
Forgejo's commits endpoint filters on `sha`, not `branch`. Sending
`?branch=<name>` was silently ignored and the API returned the default
branch's commits for every ref, so branch resolution appeared to work
while always yielding the same list.
Rename the parameter to `ref` (a branch, tag, or sha) and send it as
`sha`, documenting that the slot name is Forgejo's choice while the value
is a caller-supplied git ref.
The flat commits payload is GitHub-shaped (`sha`, `commit.message`,
`html_url`, `created`) while the nested branch commit uses `id`,
`message`, `url`, and `timestamp`. Give each Commit field an
AliasChoices/AliasPath covering both shapes so one model serves the
/branches and /commits endpoints, then map commits through it instead of
returning raw dicts under a `list[Commit]` annotation.
Also annotate get_branches' limit/page to match get_commits.
- Set --color-danger to #d93f2d (dark theme), #b01c2a (light theme)
- Added --color-danger-hover with darkened values
- Replaced magic hex in error.html with var() references
- Updated JS glow animation to match new danger color
- Removed unused tokens: primary-foreground, primary-hover, primary-muted, border-subtle
Changes .btn-primary from dark (#17191c) to red (#c62030) background
with darker red (#a81a27) on hover. Affects Open dashboard, Sign in,
Create share link, and other primary action buttons.
The .app-header .btn-borderless override was missing background:transparent,
so the red bg-danger from the base .btn-borderless leaked into nav buttons.
Reverts header-specific .btn-borderless override so Dashboard and
Settings nav buttons remain transparent with accent hover. Only
non-header borderless buttons get the red default style.
Changes .btn-borderless from transparent to red (#c62030) background
with darker red (#a81a27) on hover. Updates header-specific overrides
to match the new default style.
* Add CLI scaffold and config generators
* Add PR stacking note to README
* refactor: write embargo init command myself for clarity
* refactor: rename Myst and narrow CLI setup flow
* Update Phase 1 plans with finalized design decisions
Major updates:
- Add authentication model (Forgejo sessions for identity, PAT for data access)
- Add link types (private email-verified, public time-expired)
- Add link creation rules (owner-only)
- Add Docker/deployment guidance (Dockerfile only, Dokploy handles orchestration)
- Add database model (separate DBs on same PostgreSQL instance)
- Add viewer baseline and user dashboard sections
- Add SMTP configuration via post-login setup page
Key architectural decisions:
- Users log in via Forgejo session, no separate Myst login
- Service account PAT used for API calls, not user identity
- Private links require email verification code
- Public links are time-expired for job applications
- Myst provides Dockerfile, operators use Dokploy for deployment
* Complete CLI init skeleton with CodeRabbit review fixes
CLI changes:
- Narrow init to Myst-only config generation (no Forgejo provisioning)
- Add yoctocolors styling to CLI output
- Simplify URL validation logic (remove dead code)
- Fix typo in env.ts comment
- Remove docker-compose generator (out of scope)
- Move example config from src/ to packages/cli/examples/
- Fix CommandName type to match implemented commands only
Config changes:
- Remove databaseUrl from myst.config.json (DB is .env-only)
- Update example config with current fields
- Reject non-HTTP schemes before auto-prepending https://
- Use localhost -> 127.0.0.1 in Caddy/Nginx examples
- Add file existence checks and 0o600 permissions
Build passes after all changes.
* docs: rewrite README with Myst branding and architecture
- Add Mermaid architecture diagram
- Document two link types (private/public)
- Explain authentication model
- Provide setup steps
- Add example configuration
- Include Phase 1 completion checklist
* fix: correct Mermaid diagram syntax
* refactor: streamline README per create-readme skill guidelines
- Use blockquote for tagline
- Simplify architecture diagram labels
- Remove redundant sections (Setup, Example Config, License)
- Keep checklist as primary tracking mechanism
- Use tables for features and auth
- Reduce verbosity throughout
* cli: add preflight check and version flag
- Add preflightWriteTargets to check file existence before writing
- Remove stub commands (start, stop, status) from help text
- Add --version flag support
- Sequential file writes with preflight check
* cleanup: remove empty command stubs and test config
- Remove start.ts, stop.ts, status.ts (not implemented yet)
- Remove myst.config.json (generated during testing)
* cleanup: remove app-ini generator (Forgejo provisioning out of scope)
* cleanup: remove empty unused utility files (docker.ts, flags.ts, init.ts)
* cleanup: remove examples.ts (examples belong in docs, not deployed code)
* Docs: clarify Forgejo user PAT wording (#4)
* Docs: add diagram slot and clarify deployment examples (#6)
* docs: rename Forgejo bot configuration
* refactor(cli): improve init command error handling; change "service
account" verbaige to "dedicated forgejo user" to match Forgejo user
model;
* docs: rewrite README with Myst branding and architecture
- Add Mermaid architecture diagram
- Document two link types (private/public)
- Explain authentication model
- Provide setup steps
- Add example configuration
- Include Phase 1 completion checklist
* fix: correct Mermaid diagram syntax
* refactor: streamline README per create-readme skill guidelines
- Use blockquote for tagline
- Simplify architecture diagram labels
- Remove redundant sections (Setup, Example Config, License)
- Keep checklist as primary tracking mechanism
- Use tables for features and auth
- Reduce verbosity throughout