Opsdash - Operational Calendar Dashboard

CI runs in Forgejo Actions on the Forgejo-hosted repository.

Opsdash is an independent third-party app that turns Nextcloud Calendar data into a practical operations dashboard: what happened, what is on target, and where your time is drifting.

Opsdash is not affiliated with, endorsed by, sponsored by, or officially maintained by Nextcloud GmbH or the Nextcloud project.

🚀 Feature Rundown

• 📅 Dashboard – KPIs for week/month, busiest days, averages, weekend share, top categories, longest events, and multi-tab layouts.
• 🎯 Targets & pacing – per-calendar and per-category goals, pace hints, trend context, forecast signals, and over-target progress beyond 200%.
• ⏱️ Current period done vs planned – active week/month separates elapsed hours from future hours so “done” metrics stop at now and upcoming time stays clearly labeled.
• ⚖️ Balance – share cards, stacked bars, relations/ratios, heatmaps, lookback trends, and daypart toggles.
• 🧠 Notes – edit “This week/month”, view “Last week/month”, and optionally surface notes in cards.
• 🧩 Shared overlays – onboarding, profiles, and the in-app What's new window now share one large overlay shell and interaction model.
• ✨ Release notes in-app – new versions can auto-open a What's new view with short highlights, preview images, a clickable version history, and remembered dismissal per app version.
• 🗓️ Activity & schedule – event and active-day KPIs plus “Days off” trend heatmaps.
• 🔐 Runs inside Nextcloud – same session, same permissions, CSRF-protected writes, no external API calls.
• 🗂️ Deck widgets – a management-focused Deck cards widget plus a compact Deck stats widget, both with per-widget board/stack/tag filters and range-aware Deck summaries.
• 📨 Reporting & recap mail – configure separate weekly/monthly recap modes, trigger a live test send from the UI, and render goal-type-aware mails inside the native Nextcloud email shell.
• 📐 Widget sizing controls – per-widget width/height plus scale/dense options for layout tuning.

Screenshots

Widgets (Light)	Widgets (Dark)

Onboarding (Light)	Onboarding (Dark)

What's New Overlay

Calendar Table (Light)	Calendar Table (Dark)

Compatibility

Opsdash supports Nextcloud installations, but it is an independent third-party app and not an official Nextcloud app.

Branch	Nextcloud	App version
master	30-33	0.8.1
release/0.5.x	30-33	Store-ready line

Install

Install from the Nextcloud App Store as a third-party app (when published) or place opsdash in custom_apps/ and enable it:

occ app:enable opsdash

Development

make start
cd opsdash
npm ci
composer install
npm run build
npm run test:unit
composer run test:unit
PLAYWRIGHT_BASE_URL=http://localhost:8093 npm run test:e2e

• make start starts the local Nextcloud 33 dev container on http://localhost:8093.
• make start33 starts the same Nextcloud 33 stack explicitly.
• make start32 starts the Nextcloud 32 container on http://localhost:8092.
• make start31 starts the Nextcloud 31 container on http://localhost:8088.
• The checked-out app is mounted into the dev container from ./opsdash by default. Override with APP_SOURCE_DIR=/abs/path/to/opsdash if you need a different source path.
• make status / make logs help confirm the stack is up before testing.
• The ghcr.io/juliusknorr/nextcloud-dev-php83:latest image bootstraps the server on first start. After docker compose up -d, Apache may answer on the mapped port before Nextcloud is ready.
• On a fresh volume, wait until docker exec <container> bash -lc 'cd /var/www/html && php occ status' reports installed: true. This can take roughly 4 minutes on first bootstrap.
• Do not run php occ maintenance:install against these dev-image containers during normal startup. Use the image's built-in bootstrap flow and only intervene manually when you intentionally reset a dedicated test volume.

Mail Test Stack

For SMTP testing with a local mail catcher:

docker compose -f docker-compose33-mail.yml up -d
docker exec nc33-mailguard bash -lc 'cd /var/www/html && php occ status'

• docker-compose33-mail.yml starts a dedicated Nextcloud 33 test instance on http://localhost:8094.
• It also starts Mailpit with SMTP on localhost:1026 and the web inbox on http://localhost:8026.
• The same bootstrap rule applies here: wait for occ status to show installed: true before setting SMTP, users, or app config.
• Test-send paths:
  • UI: POST /overview/report/test-send
  • CLI payload: php occ opsdash:report --user=<uid> --range=week --offset=0 --format=json
• Report mails are goal-type-driven:
  • Single Goal
  • Calendar Goals
  • Calendar + Category Goals
• Dashboard presets/layout variants stay in the UI, but they do not affect report rendering.
• Automatic recap delivery is integrated through the Nextcloud background job system, not an app-managed Unix cron path.
• Scheduler semantics:
  • final = complete previous week/month after the period closes
  • checkpoint_final = midpoint checkpoint plus final closed-period recap
  • sendTimeLocal = user-local Nextcloud time, not raw server time
• Current defaults:
  • weekly enabled: final at 06:00
  • monthly disabled: checkpoint_final at 18:00
• Release builds intentionally expose only one Opsdash occ command: php occ opsdash:report.

Quick smoke check:

make smoke

Packaging

make release VERSION=0.8.1

One-step release helper:

• bumps appinfo/info.xml, package.json, package-lock.json, opsdash/VERSION, and SECURITY.md
• runs the packaged app build
• creates build/dist/opsdash-<version>.tar.gz

Manual packaging only:

make appstore VERSION=0.8.1

Produces build/dist/opsdash-<version>.tar.gz (unsigned).
Sign separately with:

make sign VERSION=0.8.1 SIGN_PRIVATE_KEY_FILE=/secure/path/privkey.pem SIGN_CERT_FILE=/secure/path/cert.crt SIGN_CONTAINER=nc33-dev

Upload the signed tarball with:

FORGEJO_TOKEN=<token> make upload VERSION=0.8.1 RELEASE_TAG=v0.8.1

Push to the Nextcloud App Store with:

APPSTORE_TOKEN=<token> SIGN_PRIVATE_KEY_FILE=/secure/path/privkey.pem DOWNLOAD_URL=https://public-host/opsdash-0.8.1.tar.gz make appstore-push VERSION=0.8.1

Long-form internal release and runbook documentation now lives in the separate opsdash-docs and opsdash-ops workspace repos. Keep this repo focused on the app, its generic release commands, and contributor-facing basics.

Contributing

1. Keep PRs focused.
2. Update docs and fixtures when payloads change.
3. Run unit tests before opening a PR.