Skip to content

docs(migrating): document aw-server-rust --import-legacy / --legacy-dbpath - #204

Open
TimeToBuildBob wants to merge 2 commits into
ActivityWatch:masterfrom
TimeToBuildBob:docs/import-legacy
Open

TimeToBuildBob wants to merge 2 commits into
ActivityWatch:masterfrom
TimeToBuildBob:docs/import-legacy

Conversation

@TimeToBuildBob

Copy link
Copy Markdown
Contributor

Documents the manual legacy-import path added in ActivityWatch/aw-server-rust#780 (follow-up promised on ActivityWatch/aw-server-rust#546).

  • Explains that the automatic import only runs when the aw-server-rust database is first created, and the log line that says so.
  • New "Running the import manually" subsection: aw-server-rust --import-legacy (idempotent, merges only missing events), --legacy-dbpath for non-default locations, and the custom --dbpath interaction.
  • The flags first ship in the release after v0.14.0 (#780 merged after v0.14.0 was tagged), so the old move-the-db workaround is kept for older versions.

Binary name verified against aw-server-rust's make package (aw-server → aw-server-rust). sphinx-build shows no warnings for migrating.rst.

@TimeToBuildBob

Copy link
Copy Markdown
Contributor Author

@greptileai review

@TimeToBuildBob

Copy link
Copy Markdown
Contributor Author

Updated the version wording now that it has shipped: ActivityWatch/aw-server-rust#780 (merge 692fa0a) is an ancestor of the aw-server-rust commit pinned at ActivityWatch/activitywatch v0.14.1 (04e8d66, 16 ahead / 0 behind). The doc now says "v0.14.1 and newer" instead of "released after v0.14.0", and the fallback applies to "v0.14.0 and older". Ready to merge.

@TimeToBuildBob

Copy link
Copy Markdown
Contributor Author

The red build here is unrelated to this change: apt-get install 404s because the workflow never runs apt-get update. That's fixed in #211 (green). I'll rebase this PR once #211 lands.

@TimeToBuildBob

TimeToBuildBob commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor Author

Status (updated 2026-11-17): rebased onto master now that #211 has landed. I dropped the duplicate apt-get update commit and the empty retrigger commit, so this PR is back to the two src/migrating.rst commits (head 40d8f7d), with no workflow changes. The documented flags (--import-legacy, --legacy-dbpath) and the "skipping legacy import" log line still match aw-server-rust master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant