My Weekly ToDo List - A web-based weekly task management app
mARTin-B78
6f4fe219dc
Some checks are pending
Playwright Tests / test (push) Waiting to run
There were two near-identical update scripts and they drifted: the npm ci fix from 1.114.1 only ever landed in update-app.sh, so the boot path kept running npm install. my-weekly-todo-update.service now runs update-app.sh, and boot-update.sh is a shim kept only so a not-yet-recopied unit still works. To be usable at boot the script needed three things it did not have: - Skip the rebuild when HEAD already matches origin/main and a standalone build exists, so a reboot is not a full rebuild every time (--force overrides). - Do not restart PM2 when its daemon is not up yet. At boot this unit runs before pm2-root.service, and probing with `pm2 describe` would spawn a stray daemon that races the real service, so it checks the pid file. - A flock single-instance lock, so a boot run and a manual run cannot install into the same tree at once. It also picks up prisma migrate deploy / generate and the .env copy that only the boot script had. The log moved to /var/log/my-weekly-todo-update.log. v1.115.2 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .claude | ||
| .github/workflows | ||
| .opencode | ||
| .planning | ||
| docs | ||
| prisma | ||
| public | ||
| scripts | ||
| spec | ||
| specs | ||
| src | ||
| tests | ||
| Version 01 | ||
| .dockerignore | ||
| .env.example | ||
| .env.production.save | ||
| .eslintrc.json | ||
| .gitignore | ||
| build.pid | ||
| CHANGELOG.md | ||
| CLAUDE.md | ||
| clear-data.ts | ||
| COMMIT_SUMMARY.md | ||
| comprehensive-debug.js | ||
| debug-login-page.js | ||
| debug-signup.js | ||
| deploy.sh | ||
| deployment-notes.md | ||
| docker-compose.dev.yml | ||
| docker-compose.local.yml | ||
| docker-compose.yml | ||
| Dockerfile | ||
| fill-data-v2.ts | ||
| fill-data.ts | ||
| fill-ext-events.js | ||
| fill-ext-events.ts | ||
| final_phase3_analysis.md | ||
| INFRASTRUCTURE_REQUIREMENTS.md | ||
| mock-prisma.ts | ||
| My-Weekly-ToDo-List.code-workspace | ||
| next-env.d.ts | ||
| next.config.js | ||
| opencode.json | ||
| package-lock.json | ||
| package.json | ||
| phase3_analysis.md | ||
| playwright.config.ts | ||
| postcss.config.js | ||
| query.js | ||
| README.md | ||
| SETUP.md | ||
| tailwind.config.js | ||
| TEST_PLAN_SUMMARY.md | ||
| TEST_PLAN.md | ||
| test-account-setup.js | ||
| test-api.js | ||
| test-email.js | ||
| test-route.js | ||
| test-syno.js | ||
| tsconfig.json | ||
| tsconfig.tsbuildinfo | ||
My Weekly To Do List
A web-based weekly task management application that organizes to-dos and calendar events in a single, intuitive weekly view.
Features
- Weekly view of tasks and calendar events
- Drag and drop functionality between days
- Calendar integration with Google and Apple Calendar
- Responsive design for all devices
- Accessible user interface (WCAG 2.1 AA compliant)
Deployment with Docker
This application can be deployed using Docker and Docker Compose.
Prerequisites
- Docker Engine
- Docker Compose
Quick Start
- Clone the repository and navigate to the project directory
- Build and start the containers:
docker-compose up --build - Access the application at http://localhost:3000
Environment Variables
The application requires the following environment variables:
DATABASE_URL: PostgreSQL connection stringNEXTAUTH_SECRET: Secret for NextAuth.jsNEXT_PUBLIC_BASE_URL: Public URL of the applicationMICROSOFT_CLIENT_ID: Azure AD Application (client) ID for Microsoft LoginMICROSOFT_CLIENT_SECRET: Azure AD Application secret for Microsoft Login
Database Configuration
The application uses PostgreSQL for data storage. The Docker Compose setup includes a PostgreSQL service, but you can also connect to an external database by setting the DATABASE_URL accordingly.
Building for Production
To build the production version:
docker build -t my-weekly-todo-list .
Development
For development, you can run:
npm run dev
License
This project is licensed under the MIT License.