Waters ChurchandClaude Opus 5
39c65cf9de
The deploy was the one pipeline with no failure notification. It either worked or you found out by noticing the site was stale — the same shape as the off-site backup before today. alert.js now takes CHECKLIST_ENV_FILE and CHECKLIST_NODE_MODULES, because the deploy job runs in a container that has the repo but no server/.env and no node_modules; both live on the NAS at the mounted deploy directory. What this still does not catch, and the reason it is written down in the workflow: a runner that wedges. Today the NAS runner claimed run 7, executed none of its six steps, and Gitea timed it out fifteen minutes later — every step was marked failed without one having run, so no in-job step could have reported it. The container said "Up 2 hours" throughout and admitted on restart that it had been holding the job. A stuck runner looks exactly like a slow one, and catching it needs something watching from outside the run. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
- Install Node.js (if not already installed) - Download from nodejs.org
- Navigate to the project directory:
cd recurring-checklist-app - Install dependencies:
npm install - 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
-
Add Tasks:
- Enter a title (required) and optional description
- Descriptions support multiple lines and can include detailed instructions
- Click "Add Task" or press Enter
-
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)
-
Complete Tasks:
- Check the checkbox next to an item to mark it complete
- Completed items automatically move to the "Done" section
-
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
-
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:
- Build the installer using
npm run build:win - Copy the installer file from the
distfolder - Run the installer on each Windows machine where you want to use the app
- 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