Erich Blume
b197bd5f58
## Summary Migrates the docs build pipeline to Dagger (Phase 2 of the Dagger CI adoption plan). - **Backfill `date-modified` frontmatter** on all 80 docs — Dagger's `--src=.` excludes `.git`, so Quartz can't use git history for page dates. Frontmatter dates work with or without git. - **New `docs-check-frontmatter` mise task + pre-commit hook** — validates all docs have `title`, `tags`, and `date-modified` - **New Dagger functions** — `build_changelog` (towncrier in Python container) and `build_docs` (chains changelog → Quartz build in Node container, returns tarball) - **Simplified CI workflow** — the ~44-line inline Quartz build (clone, npm ci, build, tar, cleanup) is replaced by `dagger call build-docs`. Changelog step remains local on the runner since towncrier needs to modify the host working tree for the git commit. ### Design decisions - **Towncrier runs twice in CI**: once inside Dagger (for the docs tarball) and once on the runner (for the git commit). This is intentional — Dagger's directory export is additive and can't delete the consumed changelog fragments from the host. - **Artifact hosting stays on Forgejo Releases** (not migrated to Forgejo Packages as the plan doc originally suggested). That migration can happen independently. - **`date-modified` frontmatter** preserved even though `build_changelog` installs git — the git there is only for towncrier's `git add` call, not for history. The local iteration story (`dagger call build-docs --src=. --version=dev` with uncommitted changes) depends on frontmatter dates. ### Local iteration ```bash dagger call build-docs --src=. --version=dev export --path=./docs-dev.tar.gz tar tf docs-dev.tar.gz | head -20 ``` ## Deployment and Testing - [x] `dagger call build-docs --src=. --version=dev` produces valid 1.1MB tarball (149 HTML pages) - [x] Pre-commit hooks pass (including new `docs-check-frontmatter`) - [ ] Full `workflow_dispatch` run after merge 🤖 Generated with [Claude Code](https://claude.com/claude-code) Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/157
59 lines
1.4 KiB
Markdown
59 lines
1.4 KiB
Markdown
---
|
|
title: TeslaMate
|
|
date-modified: 2026-02-07
|
|
tags:
|
|
- service
|
|
- vehicle
|
|
---
|
|
|
|
# TeslaMate
|
|
|
|
Self-hosted Tesla data logger collecting vehicle telemetry from the Tesla Owner API.
|
|
|
|
## Quick Reference
|
|
|
|
| Property | Value |
|
|
|----------|-------|
|
|
| **URL** | https://tesla.ops.eblu.me |
|
|
| **Tailscale URL** | https://tesla.tail8d86e.ts.net |
|
|
| **Namespace** | `teslamate` |
|
|
| **Image** | `teslamate/teslamate:2.2.0` |
|
|
| **Database** | [[postgresql]] |
|
|
|
|
## Data Collected
|
|
|
|
- Battery level, state of charge, range estimates
|
|
- Charging sessions (location, energy, cost, duration)
|
|
- Drives (distance, efficiency, routes)
|
|
- Climate/HVAC usage
|
|
- Software update history
|
|
- Vampire drain analysis
|
|
- Vehicle states (asleep, driving, charging, online)
|
|
|
|
## Grafana Dashboards
|
|
|
|
18 dashboards in the "TeslaMate" folder:
|
|
- Overview, Charges, Drives, Efficiency, States
|
|
- Battery Health, Vampire Drain, Statistics
|
|
- Charge Level, Locations, Trip, Mileage
|
|
- Drive Stats, Charging Stats, Projected Range
|
|
- Timeline, Updates, Visited
|
|
|
|
Dashboards use PostgreSQL datasource (not Prometheus).
|
|
|
|
## Authentication
|
|
|
|
Uses Tesla Owner API via OAuth:
|
|
1. Access https://tesla.ops.eblu.me
|
|
2. Click "Sign in with Tesla"
|
|
3. Tokens encrypted with ENCRYPTION_KEY
|
|
|
|
## Credentials
|
|
|
|
**1Password:** `TeslaMate` item with `db_password` and `api_enc_key`
|
|
|
|
## Related
|
|
|
|
- [[postgresql]] - Data storage
|
|
- [[grafana]] - Dashboards
|
|
- [[borgmatic]] - Database backup
|