Skip to content

docs: add post-install next steps and stop-before-update instructions - #190

Open
TimeToBuildBob wants to merge 1 commit into
ActivityWatch:masterfrom
TimeToBuildBob:docs/postinstall-and-safe-update-94-92
Open

TimeToBuildBob wants to merge 1 commit into
ActivityWatch:masterfrom
TimeToBuildBob:docs/postinstall-and-safe-update-94-92

Conversation

@TimeToBuildBob

Copy link
Copy Markdown
Contributor

Summary

Closes #94 and #92 (and notes that #170 is fixed on live).

#94 — updating.rst told users to "replace the files" but never said stop ActivityWatch first. Overwriting the running aw-server binary is exactly the failure mode users hit. The new Stop ActivityWatch before updating section covers every supported way to start it: aw-qt tray Quit, systemctl --user stop for the systemd path, pkill -f aw-qt/aw-server for the manual path, macOS menu-bar Quit / killall, and Windows tray Quit / Task Manager.

#92 — getting-started.rst stopped at install. The new Next steps after installing section points users at the four high-leverage things to do next:

  1. Install the browser extension (aw-watcher-web) — Chrome/Edge/Brave and Firefox store links.
  2. Install an editor watcher — link into the editor-watchers section of watchers.rst.
  3. Set up categories — both the web UI Settings panel and the categories.yaml config file, with a pointer to configuration.rst.
  4. Where data lives — back up / wipe-and-restart note, link to directories.rst.

#170 — verified on the live site that the fix is in production: docs.activitywatch.net/en/latest/search.html now loads _static/jquery.js and searchindex.js returns HTTP 200 with content; the sphinxcontrib-jquery extension is doing its job. No code change needed, just a verification note.

Why

Both #94 and #92 are 2020-vintage issues that have stayed open because the bar is "small but multi-section" docs work that's easy to defer. New users hit both within their first hour.

Test plan

  • make html (via uvx --with sphinx + extensions) builds with no new warnings on either modified file. (The pre-existing 124 warnings are all aw-core/aw-server/aw-client autodoc imports and autosectionlabel collisions from headings that already exist in master — unrelated.)
  • Live docs.activitywatch.net search verified: jQuery loads, searchindex.js serves.
  • Visual: I'll attach screenshots of the rendered getting-started.html and updating.html shortly.

Closes ActivityWatch#94 (updating.rst should explain how to stop
ActivityWatch before replacing files) and ActivityWatch#92
(getting-started should mention what to do after installing).

- updating.rst: add 'Stop ActivityWatch before updating' section covering
  aw-qt tray Quit, systemd --user stop, pkill, macOS menu bar / killall,
  and Windows Task Manager, before the existing macOS-only note.

- getting-started.rst: add 'Next steps after installing' section covering
  the browser extension (with store links), editor watchers (link to
  watchers.rst), setting up categories (web UI + categories.yaml), and
  where data lives (link to directories.rst).

- docs#170 verified fixed on live site: docs.activitywatch.net search.html
  loads jquery.js and searchindex.js returns 200; the sphinxcontrib-jquery
  fix is in production.

Git-Session-Id: c8ba
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.

Documentation about updating should contain information how to stop application

1 participant