Repository navigation
Mark Zero retired and point new apps to First #113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,10 +1,12 @@ | ||
| --- | ||
| title: Dynamic sites with Zero | ||
| description: Zero is the runtime a Space gets when its project declares it. A database, HTTP endpoints, live queries, crons, and storage, from one TypeScript app. | ||
| title: Zero | ||
| description: Zero is retired. Spaces that run it keep working, and Zero 0.9, its last release, moves apps to First. | ||
| sidebar: | ||
| order: 0 | ||
| --- | ||
|
|
||
| **Zero is retired.** Spaces that run a Zero app keep serving, and you can keep publishing them. Zero 0.9 will be its last release apart from security fixes, and it exists to move Zero apps to First, Zero's successor. Start new apps on First: see the [First docs](https://first-docs.space.fast/). | ||
|
|
||
| Zero is available on every account, with [usage allowances and metered rates](/usage). To use it, declare the full [runtime block](#declare-it) in `sf.jsonc` and provide the server entry. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🟡 Bug · Other pages still steer new apps to Zero This paragraph still reads as if Zero is current ( Found by Indent Review Agent |
||
|
|
||
| ## What Zero is | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -17,7 +17,7 @@ A build turns source code into publishable output. You can build locally or let | |
|
|
||
| ## Capsule | ||
|
|
||
| The compiled form of a Zero app. `sf publish` turns your TypeScript server code into a capsule, which the platform installs on the Space. See [Dynamic sites with Zero](/zero-runtime). | ||
| The compiled form of a Zero app. `sf publish` turns your TypeScript server code into a capsule, which the platform installs on the Space. See [Zero](/zero-runtime). | ||
|
|
||
| ## Claim / claiming | ||
|
|
||
|
|
@@ -53,4 +53,4 @@ An immutable snapshot created when a publish produces a new version. A ready ver | |
|
|
||
| ## Zero | ||
|
|
||
| The runtime for an app with live queries and a declared database schema. One TypeScript app compiles into a [capsule](#capsule) with a MySQL database next to your code. [Functions](#functions) also provides a database, and [crons](/crons) can call either runtime or static files. See [Dynamic sites with Zero](/zero-runtime). | ||
| The retired runtime for an app with live queries and a declared database schema. Spaces that run it keep working, and Zero 0.9, its last release, moves apps to First. One TypeScript app compiles into a [capsule](#capsule) with a MySQL database next to your code. [Functions](#functions) also provides a database, and [crons](/crons) can call either runtime or static files. See [Zero](/zero-runtime). | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Preserve the retirement support details. The glossary calls 0.9 the last release without the security-fix exception. It also omits that existing apps can still be published. Add both details so readers do not mistake retirement for an end to updates or publishing. Add the exception to the description in Based on learnings: preserve scope and exceptions and reconcile glossary entries.
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 Bug · First docs link returns 404
This URL returns
HTTP/2 404right now, so readers who follow the advice to start on First hit a dead page. No repo gate checks external links (verify-public-safety.mjs only checks for private GitHub URLs). Hold the merge until the First docs Space is live, or link to a page that exists today and swap it later.Found by Indent Review Agent