Updating the Recurring Checklist server

5-minute guide for pushing new app versions to the Synology NAS

Before you start

The 5 steps

1Open File Station on Chronicles-NA and navigate to:

docker  →  recurring-checklist

2Drag the new checklist-deploy.tgz into that folder. If File Station asks about overwriting, choose Overwrite.

3Extract it — Synology does this in two passes:

  1. Right-click checklist-deploy.tgz → Extract → Extract here. A checklist-deploy.tar appears next to it.
  2. Right-click checklist-deploy.tar → Extract → Extract here. When it asks about overwriting files, say “Overwrite all” or “Yes to all”.
Don’t worry about overwriting. The tarball is built so it can’t touch .env or data/. The only files that change are the app code: server.js, public/*, Dockerfile, etc.

4Clean up the leftovers. Delete:

5Rebuild the container in Container Manager:

  1. Open Container Manager.
  2. Click Project in the left sidebar.
  3. Click the row recurring-checklist to select it.
  4. Click the Action dropdown above the list → choose Build.
  5. A log window pops up. Wait ~30–60 seconds until you see Exit Code: 0 at the bottom. Click Close.

Verify it worked

  1. Open https://check.watersmedia.org in a browser.
  2. Hard-refresh with Cmd + Shift + R (or Ctrl + Shift + R on Windows). This clears any cached old JavaScript.
  3. The page should load normally, with whatever new feature the developer described in the release.

If something looks broken

  1. Check container logs. Container Manager → Container tab → recurring-checklist → Details → Log tab. Look for red error lines near the bottom.
  2. Restart the container. Container Manager → Project → recurring-checklist → Action → Stop, then Action → Start.
  3. Restore your data if a release accidentally corrupted state: Hyper Backup → Recurring Checklist task → Restore Data → pick a recent backup → restore just the data/ folder.
  4. Roll back. Keep the previous release’s .tgz archived. To roll back, extract it over the current code (overwriting), then rebuild. Your data stays intact.
Always keep the previous release’s .tgz for at least a week. If a new release introduces a bug, you can roll back in under a minute by extracting the old one and rebuilding.

Quick reference