Updates: what changed, and when
Update dates come from frontmatter, not hand-copied text. Also covers how updates work, what a version means, how corrections are handled and why there is no “always current” claim.
Updated 2026-11-16
| Page | Path | Last updated |
|---|---|---|
| The idle machine at home can run an AI assistant | /en | 2026-11-16 |
| About localdeploy.dev | /en/about | 2026-11-16 |
| Cloudflare basics: domains, IPs, Pages, Workers and Tunnel | /en/cloudflare | 2026-11-16 |
| Contact: what to send, when to expect a reply | /en/contact | 2026-11-16 |
| Terms and privacy | /en/legal | 2026-11-16 |
| Pricing: quoted by scope, not a fixed bundle | /en/pricing | 2026-11-16 |
| Cancellation and refunds | /en/refund | 2026-11-16 |
| Home-lab security: do the few things that prevent most incidents | /en/security | 2026-11-16 |
| Deployment packages: getting the local AI running | /en/services | 2026-11-16 |
| System and hardware choices: Debian, Proxmox, fnOS, TrueNAS or Flatcar? | /en/systems | 2026-11-16 |
| Updates: what changed, and when | /en/updates | 2026-11-16 |
Dates come from each page's frontmatter, so they change only when the content does.
Where the dates come from
Each page has updatedAt in frontmatter. The build renders it into the page and the Markdown mirror, so the date cannot drift from the content. The table above comes from the same source.
When a page is updated
- Substantive changes: a new section, a correction, a changed command or configuration.
- Upstream changes: a Cloudflare, Traefik or Harbor interface or default changes enough to make the text wrong.
- Reader feedback: someone points out an unclear or stale passage, and it is confirmed.
Typos and layout changes update the date too, because the content did change for the reader.
Why there is no “always current”
Systems, drivers, models and cloud services change. Any document claiming to be forever current is not credible. What this site can promise:
- every page has a visible update date;
- corrections are made and dated on this page;
- a paid delivery is tied to the version and quote confirmed at the time, not to future compatibility.
Versions of a paid package
A paid package has its own version and delivery description. A change in scope or deliverables is confirmed as a new version or a new quote; confirmed work is not silently rewritten.
Reporting an error
Email hello@localdeploy.dev with:
- the page URL or title;
- what is wrong (command, output, a description of a screenshot);
- your environment (system, version, relevant configuration).
After confirming, the page is updated; if a paid delivery is affected, the handling is explained separately.
Recent updates
- 2026-11-16: first version of the site: free basics, packages, pricing, contact, cancellation and legal pages, the hardware assessment, and Chinese/English counterparts.
Not sure where to start?
Run the assessment first, or send your setup and goal by email. The reply says whether it fits and what happens next.