Not me significantly glancing at my #selfhosted #forgego again.
I should actually calculate the 9s on that thing so I can say with confidence that it has better uptime than GitHub.
Not me significantly glancing at my #selfhosted #forgego again.
I should actually calculate the 9s on that thing so I can say with confidence that it has better uptime than GitHub.
A lot shipped in Forge recently.
Token management is live β named, revocable bearer tokens with SHA-256 fingerprinting. The MCP demo shows Claude creating content in real time.
Two AI safety improvements: Forge now blocks revoking your last admin token. Fields tell agents what format they expect β Markdown or HTML β directly in the tool description.
https://forge-cms.dev/devlog/from-templates-to-token-safety-what-shipped-since-shared-partials
Forge v1.3.0 is out.
forge.HeadAssets β declare preconnects, stylesheets, favicons, and scripts once in app.SEO(). Injected into every page automatically.
github.com/forge-cms/forge/releases/tag/v1.3.0
Phase 2 begins
https://forge-cms.dev/devlog/phase-2-begins-mustconfig-ogdefaults-appschema-shared-partials
Forge v1.2.0 is out.
App.Partials() β one directory, shared across every module template. App.MustParseTemplate() brings the same partials and forge:head to custom route handlers.
github.com/forge-cms/forge/releases/tag/v1.2.0
Prompt that delivered real value today:
"Do any of these fixes reveal patterns worth reviewing across the existing codebase?"
Result: a structured audit that surfaced two silent failure patterns I wasn't looking for.
The best AI prompt isn't always the most sophisticated one. It's the one that asks the question you didn't know you needed to ask.