Files
Django_TasksApp/main
..
2026-10-03 21:29:16 +02:00
2026-10-03 20:37:04 +02:00
2026-10-03 20:41:45 +02:00
2026-10-03 20:53:54 +02:00
2026-09-30 17:25:25 +02:00
2026-10-03 17:11:31 +02:00
2026-10-03 17:11:31 +02:00

Tasknest development notes

Weather scheduling

The server gets a finite 16-day daily forecast from Open-Meteo and caches each user's normalized forecast for twelve hours. No browser code, template, or model calls Open-Meteo directly.

  • Dry rejects a day with precipitation probability of 40% or more, or 0.5 mm or more precipitation.
  • Sunny / mostly sunny also requires a clear/partly-cloudy condition and at least four hours of sunshine.
  • Warm requires a maximum temperature of at least 15 °C.
  • Dry and warm requires both of the corresponding rules.

If no forecast is available, a weather-dependent task remains visible rather than being treated as unsuitable. If a forecast finds an unsuitable natural occurrence, Tasknest creates a weather-owned occurrence shift to the first suitable vacancy in the finite forecast horizon. Natural recurrences and existing weather shifts are skipped, so an occurrence is never duplicated. The original recurrence anchor is not changed.

Deferral precedence is: manual, missed, and Sick Day state are evaluated before weather movement. Weather never overwrites those sources. Weather shifts are stored separately in TaskWeatherShift, so they can be recalculated without modifying user-owned deferrals.

Legacy ownership migration

Migration 0006 assigns old unowned tasks only when the database has exactly one active user. This local development database met that condition and its two existing tasks were assigned to that account. In a multi-user deployment the migration deliberately leaves legacy rows unowned instead of guessing; claim them explicitly before making ownership non-null at the database level.

Demo account reset

Create or reset the public demonstration account and its dummy data with:

/home/jorenmartijn/django/tasksnest/bin/python /home/jorenmartijn/django/main/manage.py seed_demo

The command resets only the demo account (default password: demo). It creates sample parent/subtasks, workouts, pain and sleep check-ins, and a 16-hour fasting schedule. It is idempotent: running it again removes demo-only edits and restores the same baseline. Use --username and --password to override the credentials.

A daily systemd timer template is provided in main/deploy/systemd/. Adjust the User, WorkingDirectory, and ExecStart paths in the service file if needed, then install it with:

sudo cp main/deploy/systemd/tasknest-demo-seed.service /etc/systemd/system/
sudo cp main/deploy/systemd/tasknest-demo-seed.timer /etc/systemd/system/
sudo systemctl daemon-reload
sudo systemctl enable --now tasknest-demo-seed.timer
systemctl list-timers tasknest-demo-seed.timer

The supplied timer runs daily at 03:15 Europe/Amsterdam and catches up after a missed scheduled run when the host comes back online.

Fasting phase notifications

The notify_fasting_phases command checks each active fasting schedule and sends an ntfy notification when the current phase changes to fasting or eating. It requires a tested, enabled ntfy topic in Settings. The command records each phase boundary so repeated runs do not send duplicate notifications. A failed delivery is retried on the next run. If the host was offline across several boundaries, only the current phase is announced.

The host runs Python 3.12 while the development environment uses Python 3.13. Create a separate host virtualenv so systemd does not follow a symlink to a Python executable absent from the host:

cd /home/jorenmartijn/django
python3 -m venv tasksnest-host
tasksnest-host/bin/python -m pip install -r main/requirements.txt
tasksnest-host/bin/python main/manage.py check

Install the provided systemd service and timer to run this check every minute:

sudo cp main/deploy/systemd/tasknest-fasting-notifications.{service,timer} /etc/systemd/system/
sudo systemctl daemon-reload
sudo systemctl enable --now tasknest-fasting-notifications.timer

Run database migrations before enabling the timer. Adjust the service's user and paths for your deployment.

Gitea activity widget

The main task page shows a contribution grid below Daily Workout when GITEA_USERNAME is set in the Django server process environment. It uses Gitea's /api/v1/users/{username}/heatmap endpoint, refreshes the server-side cache every 15 minutes, and keeps any token out of browser requests.

Put these values in /home/jorenmartijn/django/.env, then restart the service that runs Django. Values set directly in the service environment take priority:

GITEA_USERNAME=your-gitea-username
GITEA_BASE_URL=https://git.jorendegraaf.eu
# Only if the public heatmap endpoint does not show the activity you want:
GITEA_TOKEN=your-read-only-token

The base URL already defaults to https://git.jorendegraaf.eu. For public activity, try without a token first. If Gitea requires authentication or you want activity visible only to your account, create a token in Gitea's User Settings → Applications → Generate New Token with read:user permission. Store it in the Django service environment, never in this repository or in browser JavaScript. The dashboard shows a short unavailable message if the endpoint cannot be reached.