Waters ChurchandClaude Opus 5 00c2ad15a7
Deploy web to NAS / deploy (push) Failing after 3s
Deploy the web app from a push to main
Until now a server change reached the NAS only when someone ran ./release.sh --web
from a machine on the church network. That made the deploy depend on which laptop
was awake and where it was, which is the same fragility that let the nightly Drive
backup go stale unnoticed.

An act_runner now runs in Docker on the NAS itself and picks up this workflow, so
a push to main rebuilds the container regardless of where the push came from.

The workflow keeps the protections the old remote deploy script had, because they
are the ones that matter: server/data and server/.env are excluded from the copy
and then explicitly checked for afterwards, and the container is recreated with
'up -d --build' rather than 'down' first, so an interrupted deploy leaves the old
container serving instead of tearing the stack down. rsync runs without --delete,
matching the tarball deploy it replaces — a stale file is survivable, a wiped
data/ is not.

This covers the web app only. The iOS and Android apps bundle a copy of the UI at
build time, so they still need ./release.sh and a store release; server-side
changes reach them immediately, since they call this same server live.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-24 13:57:31 -04:00

Recurring Checklist Application

A simple Windows desktop application for managing recurring checklists. Perfect for tasks that need to be completed on a regular schedule, similar to Planning Center checklists but dedicated and simplified.

Features

  • ✅ Add checklist items with titles and detailed descriptions
  • ✅ Mark items as complete (moves to "Done" section)
  • ✅ Set items to recur daily, weekly, or monthly
  • ✅ Automatic reset of recurring items based on schedule
  • ✅ Dark theme interface matching Planning Center style
  • ✅ Card-based layout with clear visibility
  • ✅ Data persistence across sessions
  • ✅ Easy to package and distribute to multiple machines

Installation

Development Setup

  1. Install Node.js (if not already installed) - Download from nodejs.org
  2. Navigate to the project directory:
    cd recurring-checklist-app
    
  3. Install dependencies:
    npm install
    
  4. Run the application:
    npm start
    

Building for Windows Distribution

To create a Windows executable installer:

npm run build:win

This will create an installer in the dist folder that you can distribute to other machines. The installer will be named something like Recurring Checklist Setup 1.0.0.exe.

Usage

  1. Add Tasks:

    • Enter a title (required) and optional description
    • Descriptions support multiple lines and can include detailed instructions
    • Click "Add Task" or press Enter
  2. Set Recurrence:

    • Check "Recurring Task" checkbox
    • Select frequency: Daily, Weekly, or Monthly
    • For weekly: Choose the day of the week (e.g., Sunday)
    • For monthly: Choose the day of the month (1-31)
  3. Complete Tasks:

    • Check the checkbox next to an item to mark it complete
    • Completed items automatically move to the "Done" section
  4. Recurring Reset:

    • Recurring items automatically reset based on their schedule
    • Daily items reset each day
    • Weekly items reset on their specified day
    • Monthly items reset on their specified day of the month
  5. Delete Tasks:

    • Click the "Delete" button on any task to remove it permanently

Recurrence Options

  • Daily: Item resets every day at midnight
  • Weekly: Item resets on a specific day of the week (e.g., every Sunday)
  • Monthly: Item resets on a specific day of the month (e.g., day 1)

Data Storage

All checklist data is stored locally on your machine using electron-store. Data persists between application sessions and is stored in your user data directory.

Distribution

The built application can be easily copied to other Windows machines:

  1. Build the installer using npm run build:win
  2. Copy the installer file from the dist folder
  3. Run the installer on each Windows machine where you want to use the app
  4. Each installation will have its own independent data storage

Requirements

  • Windows 7 or later
  • Node.js (for development and building only)

Notes

  • The application checks for recurring items every minute
  • Recurring items reset based on the current date/time
  • Each machine will have its own separate checklist data
  • The app uses a dark theme similar to Planning Center for better visibility
S
Description
Recurring checklist for Waters Church — Node/Express web app served from the NAS in Docker, plus the Capacitor iOS and Android apps that wrap it. Deploys with release.sh.
Readme
5.3 MiB
Languages
JavaScript 71.9%
CSS 11.7%
HTML 11%
Shell 4.7%
Swift 0.5%
Other 0.1%