opsdash-app/opsdash/tools

Opsdash Tools (Dev/QA Only)

Utility scripts that are not shipped in the production app. Use them for local dev, CI seeding, and fixture capture. Safe to re-run; none of this is wired into runtime code.

Seed everything (calendars + Deck)

Run inside a Nextcloud container (adjust names/paths as needed):

docker exec -it nc31-dev bash -lc '
  cd /var/www/html &&
  BASE=http://localhost:8088 \
  ADMIN_USER=admin ADMIN_PASS=admin \
  QA_USER=qa QA_PASS=qa \
  QA2_USER=qa2 QA2_PASS=qa2 \
  WEEKS=4 \
  APP_PATH=/var/www/html/apps-extra/opsdash \
  bash /var/www/html/apps-extra/opsdash/tools/seed_opsdash.sh
'

• Seeds users (admin/qa/qa2), calendars (3–5 per user), and 5 Deck boards with open/done/archived cards.
• Past-only events for the last WEEKS (default 4), realistic work + weekend mix. No future events. Re-runs reuse boards/titles.
• NC_ROOT auto-resolved by the script; override if needed.

Capture fixtures (after seeding)

BASE=http://localhost:8088 ADMIN_USER=admin ADMIN_PASS=admin \
  bash tools/capture_opsdash_fixtures.sh

Writes tools/fixtures/load-week.json, load-month.json, deck-boards.json.

Screenshot-ready feed

• For README/marketplace assets, prefer the balanced demo feed in SCREENSHOT_FEEDS.md.
• Seed it inside the Nextcloud container/app checkout with:

BASE=http://localhost USER=admin PASS=admin WEEKS=4 \
  bash /var/www/html/apps-extra/opsdash/tools/seed_screenshot_feed.sh

• This feed is past-only: the last WEEKS including today, with future days in the current week intentionally skipped.
• The script prints the exact onboarding mapping after seeding:
  • Work -> Opsdash · Deep Work + Opsdash · Meetings
  • Hobby -> Opsdash · Personal + Opsdash · Learning
  • Sport -> Opsdash · Sport + Opsdash · Recovery

CI usage

• .forgejo/workflows/server-tests.yml runs tools/seed_opsdash.sh after starting the PHP server so Playwright always sees seeded data.
• Keep tooling here; do not bundle in runtime artifacts or app packages.

Frontend asset rule

• Keep app-wide stylesheet changes in css/style.css and load them through the normal Nextcloud path in OverviewController with \OCP\Util::addStyle($appName, 'style').
• Do not move the main stylesheet into a custom Vite CSS manifest flow just to solve a local cache symptom. For Opsdash, the Nextcloud-standard css/style.css path is the intended source of truth.
• After changing css/style.css, rebuild JS if needed and do a hard reload when verifying in a browser session that already had Opsdash open. The stylesheet URL stays stable, so dev-time browser cache can mislead you into thinking Docker did not pick up the change.