Waters ChurchandClaude Opus 5 3d82e46951 Make the off-site backup find Drive, and say so when it cannot
The nightly copy to Drive had been dead since 15 September. DRIVE_DIR pointed at
Apps/Backups/Checklist Backups; the folder is Apps/Checklist Backups, with no
Backups level. The guard for a missing folder did its job and exited — into a
logfile nobody reads, so from the outside a broken backup and a healthy no-op
looked identical. Eight days were missing; this run copied them.

That is the second time the same failure has hidden in the same place. The
header comment already records the first: ten weeks stale in July, found in
September. Correcting the path alone would leave the mechanism that hid it
untouched, so:

- The Drive folder is probed rather than hard-coded, across every mounted
  GoogleDrive-* account and both known folder layouts. The laptop mounts
  christian@ where the Studio mounts media@, and the folder has moved once
  already, so a literal path is the wrong thing to depend on.
- Every failure now emails as well as logs, via scripts/alert.js, which reuses
  the server's own SMTP settings. A failed alert never masks the failure it was
  reporting.
- A run that does not error but leaves the newest off-site copy more than
  STALE_DAYS old now alerts too. That is the check that would have caught both
  incidents; the error paths only fire when the script actually runs.

What this still cannot catch is the script never running at all — a sleeping
Mac or an unloaded LaunchAgent is silent by construction.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-24 14:16:50 -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%