Skip to content
Skills Library
DevOps & cloud · Automation

update-server

/update-server

Update installed apps (pull new images / brew upgrade) and Server OS itself, safely. Use for "update everything", "upgrade X", "is there a new version", monthly maintenance.

Repository
server-os ↗
Licence
MIT
Last repository change
03.11.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content21 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 03.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Update installed apps (pull new images / brew upgrade) and Server OS itself, safely. Use for "update everything", "upgrade X", "is there a new version", monthly maintenance.

Triggers from the description

update everythingupgrade Xis there a new version
Original author description

Update installed apps (pull new images / brew upgrade) and Server OS itself, safely. Use for "update everything", "upgrade X", "is there a new version", monthly maintenance.

How it works

SKILL.md has no level-two headings · 23 lines, 300 words

SKILL.md preview
---
name: update-server
description: Update installed apps (pull new images / brew upgrade) and Server OS itself, safely. Use for "update everything", "upgrade X", "is there a new version", monthly maintenance.
---

# Update the server

1. **Inventory:** `list_apps` and `../apps/*/app.yaml`, which give the method (compose / brew) per app.
2. **Docker apps:** for each `../apps/<id>/compose.yaml`:
   - `docker compose -p sd-<id> -f compose.yaml pull`;
   - if a new image arrived, `docker compose -p sd-<id> -f compose.yaml up -d`;
   - check the app answers.
   - One app at a time. Never update a database container together with its app without reading the release notes.
3. **Homebrew:** `brew outdated`, then `brew upgrade <formula>` for the server's formulae only (the ones in `app.yaml` files), then `brew services restart <formula>`.
4. **Server OS itself:** use the built-in updater. Never `git pull` or copy files into the install yourself.
   - `update_check`: it returns `current`, `latest` (tag, release notes), `updateAvailable`, `canApply` and `blocked`.
   - If `blocked` is set, tell the owner what it says. Homebrew means `brew upgrade server-os`, Docker means pull the
     image, and a git checkout is developer mode, where the owner updates it themselves. Stop there.
   - Otherwise summarize the release notes for the owner and ask before applying. A major version, or a beta, always
     needs a yes.
   - `update_apply` starts it. The updater verifies the signature, unpacks the new version, switches over, restarts and
     rolls back by itself if the new version doesn't answer within about 45 s. The restart drops your connection: wait
     about a minute, then `update_status`. `last` says `ok`, or the `reason` and `rolledBack`.
   - Don't apply the same version again after a rollback. Report the reason; `../logs/update.log` has the details.
5. Record each app update with `audit_note` (Server OS's own updates are audited by the updater) (`app.update`, target = app + old→new version). Report what changed and anything that failed.
6. Ask first if an update is a major version, or the owner relies on the app right now.

Versions

The database has no other skills named update-server.

Database snapshot: 13.11.2026 · package version 32671df2149f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90ro-upgrade
    Safely update a customized rAthena server with upstream changes - plan, branch, merge or rebase, resolve conflicts, rebuild, migrate the database, retest. Use when the user says "update rAthena", "pull latest rathena", "merge upstream", "upgrade my server", "my fork is behind",…
  • 100vstack-upgrade
    Self-updates the Schengen-master skills toolkit to the latest version. Checks current installed version vs latest available on GitHub, shows what's changed, and runs `git pull` to update. Idempotent — safe to run repeatedly. Use when the user wants to pull in new skills, when…
  • 95mb-update
    Update Main Branch. Use when the user says update, upgrade, pull latest, get latest Main Branch, asks whether they are current, or after Devon announces a new release.
  • 100update-nuget-packages
    Vet and apply NuGet package updates safely. Use when asked to update, bump, upgrade or check NuGet packages.
  • 100qdrant-version-upgrade
    Covers upgrading Qdrant server and SDKs without interrupting availability or losing data integrity. Use when someone asks 'how do I upgrade Qdrant', 'can I jump from 1.15 to 1.18', 'rolling upgrade without downtime', 'do I upgrade the client or the server first', 'which SDK…
  • 95upgrade-cloud-composer
    Upgrade Cloud Composer (Apache Airflow) to a new version. Use when the user asks to upgrade, update, or bump Airflow, Cloud Composer, or Airflow dependencies to a new version. Handles updating terraform config and Python dependencies.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.