mirror of
https://github.com/getpaseo/paseo.git
synced 2026-07-29 12:01:31 +00:00
* docs: rename to lowercase + drop leftover plans Rename docs in docs/ to lowercase kebab-case for consistency and update all references in CLAUDE.md, CONTRIBUTING.md, CHANGELOG.md, packages/server/CLAUDE.md, and inter-doc links. Drop two leftover design plan docs: - docs/ATTACHMENT_BASED_REVIEW_CONTEXT_PLAN.md - docs/plan-approval-normalization.md * docs: drop stale uppercase entries from case-insensitive rename * feat(website): power /docs from public-docs/ markdown tree Move website docs out of TSX route components and into a root-level public-docs/ directory of plain markdown files with frontmatter (title, description, nav, order). - Add packages/website/src/docs.ts loader using import.meta.glob with ?raw to compile the markdown into the bundle at build time. - Replace the 9 hand-written docs/*.tsx routes with a single $.tsx catch-all that renders any slug via react-markdown. - Drive the docs sidebar nav from frontmatter order/nav. - Auto-discover docs routes in vite.config.ts so the sitemap stays in sync without manual edits. * fix(website): bind dev server to 0.0.0.0 so port collisions trigger fallback `host: "127.0.0.1"` (or unset) lets macOS coexist with another process holding an IPv6 dual-stack `*:8082` socket, so Vite never sees EADDRINUSE and silently binds alongside it. Forcing IPv4 wildcard makes the conflict real, and Vite's default `strictPort: false` falls through to the next free port. * fix(website): restore docs page styling after markdown migration Add a .docs-prose class that mirrors the styling the original docs/*.tsx components hand-rolled (h1/h2/h3 sizes, paragraph/list spacing, link colors, code blocks, callout-style blockquotes). ReactMarkdown was emitting unstyled HTML because the previous wrapper class only had inline-code rules — headings and code blocks fell back to user-agent defaults.
43 lines
1021 B
Markdown
43 lines
1021 B
Markdown
---
|
|
title: Updates
|
|
description: How to update Paseo daemon and apps across web, desktop, and mobile.
|
|
nav: Updates
|
|
order: 2
|
|
---
|
|
|
|
# Updates
|
|
|
|
Keep your daemon and apps current to get the latest fixes and features.
|
|
|
|
## Version compatibility
|
|
|
|
For now, daemon and app versions should be kept in lockstep. If your daemon is version X, make sure your clients are also version X.
|
|
|
|
## Update the daemon
|
|
|
|
Install the latest CLI/daemon package globally:
|
|
|
|
```bash
|
|
npm install -g @getpaseo/cli@latest
|
|
```
|
|
|
|
Then restart the daemon:
|
|
|
|
```bash
|
|
paseo daemon restart
|
|
```
|
|
|
|
## Web app
|
|
|
|
[app.paseo.sh](https://app.paseo.sh) is always up to date. No manual update needed.
|
|
|
|
## Desktop app
|
|
|
|
Download the latest desktop build from the GitHub releases page and install it over your current version.
|
|
|
|
[Paseo releases](https://github.com/getpaseo/paseo/releases)
|
|
|
|
## Mobile apps
|
|
|
|
Mobile apps are available on the App Store and Play Store. Update through your respective store. Store versions may lag behind the latest release due to review processes.
|