ActivityWatch/aw-webui — 155★ trên GitHub (TypeScript). Webapp for visualizing and browsing ActivityWatch data, built with Vue.js.
Tóm tắt dựng từ metadata GitHub của chính dự án — chưa có bài review TopGit. Trang sẽ tự động cập nhật khi bài review đầy đủ được xuất bản.
VÌ SAO CHƯA CÓ REVIEW
TopGit viết bài đầy đủ cho repo có nhiều sao nhất và được yêu cầu nhiều nhất. Trang này là snapshot trong thời gian chờ — xem README gốc ở tab READ ME.
A web-based UI for ActivityWatch, built with Vue.js
Getting started
Getting started with setting up the development environment is pretty straightforward:
# Start an instance of aw-server running in testing mode (on port 5666, with a separate database),
# This is what the web UI will connect to by default when run in development mode.
aw-qt --testing
# or, to run without watchers:
aw-server --testing
# Install dependencies
npm install
# or, to get exact versions of dependencies:
npm ci
# start aw-webui in dev mode
npm run serve
Alternatively, you can run make dev to install dependencies and serve the application locally.
You might have to configure CORS for it to work, see the CORS section below.
You may also want to generate fake data so you have something to test with, see: https://github.com/ActivityWatch/aw-fakedata/
Building
To build the production bundle, simply run the following:
# Install dependencies
npm ci
# Build for production
npm run build
Using a pre-release with your main install
Note: Running a development version of aw-webui with an old aw-server can lead to issues due to version incompatibilities.
By copying the web-assets to your main install
You can run a development version of aw-webui with your main version of ActivityWatch by building it (or fetching the latest build from CI) and replacing the contents of the static directory of your aw-server (or aw-server-rust) installation. For simplicity, back up the original directory for easier switching back.
The assets are stored in the following directories (relative to your installation directory), depending on if you use aw-server-python (default) or aw-server-rust:
You can copy the assets manually from your make build or npm run build output to the above locations.
Once you've put the files in the directories, you may have to do a hard refresh in your browser to invalidate any stale caches.
Using --webpath with aw-server-rust
Instead of copying files, aw-server-rust supports loading the web UI from a custom path via the --webpath flag. This is especially useful on platforms where the server bundles static assets into the executable (e.g. Windows):
# Point aw-server-rust to your local build output
aw-server-rust --webpath /path/to/aw-webui/dist
This avoids having to copy files and makes it easy to switch between development and production builds.
Using your main install's data
If you want to actively iterate on aw-webui with your local production data (with your production server running), you'll want to use a development build, automatically update it, and connect to your production data. To do this, in aw-webui source directory, in one terminal window run:
If you want to add debugger statements in your code and otherwise break linting rules, you'll need to add a --skip-plugins=no-debugger to that command.
Then, in another terminal (with your venv activated) run:
Distributions that need their own categorization scheme (a research build, a
company-wide deployment, ...) can ship one or more preset category sets with
the bundle, instead of patching the built-in defaults:
AW_PRESET_CATEGORY_SETS="$(cat mypreset.json)" npm run build
where mypreset.json holds a list of category sets (the same shape the
categorization settings page imports/exports):
When a build ships presets, the first preset in the list is active by
default on installs with no stored categorization. Remaining presets are
available in Settings → Categorization for the user to enable. Users who
already configured categories keep theirs — presets only show up as additional
sets. A set the user has edited and saved always wins over the preset definition
with the same id.
Embedders that can set a global before the app boots (Tauri, Android WebView,
custom launchers) may instead assign the same payload to
window.__AW_PRESET_CATEGORY_SETS__, which avoids rebuilding the bundle.
Regex compatibility note: preset regexes are validated against JavaScript
syntax, but they are also passed to the Python-backed categorization engine for
server-side queries. Use patterns compatible with both engines: basic groups,
quantifiers, character classes, and anchors are safe. Avoid JS-only
constructs such as named-capture-group syntax ((?<name>...)) — use the
Python form ((?P<name>...)) or omit named groups entirely.
Malformed presets are logged and ignored rather than breaking the UI.
See src/util/presetCategories.ts.
Tests
Tests can be run with:
npm test
The Sunburst Clock uses local wall-clock coordinates, even when the reporting
day starts after midnight. On DST changes, missing local hours remain empty
and repeated local hours overlap on the same dial sector. Arcs split at offset
transitions; event data and elapsed hover durations are unchanged. The query
window still runs from the selected start to the same time on the next calendar
day (not a fixed 24 elapsed hours).
Run its deterministic DST regressions in a separate timezone-configured process
(the CI test matrix also runs this command):
There are also E2E tests. You need to have an aw-server and the web UI running in development mode (with npm run serve, as instructed above). After you have that setup, you can run the tests with:
make test-e2e
Development
CORS
For development, you'll also have to add/change CORS configuration in the aw-server configs by adding cors_origins = http://localhost:27180 to your
configuration file /activitywatch/aw-server/aw-server.toml under respective sections (server-testing section when running server in testing mode).
Code structure
One of the first things that happen in the application is the execution of src/main.js. This loads things such as bootstrap-vue and a bunch of other stuff that's globally used (filters, resources).
The main.js file then loads the src/App.vue file, which is the root component of the application.
ActivityWatch/aw-webui có 155 sao GitHub — tải lại trang để xem số mới nhất, hoặc xem trực tiếp github.com/ActivityWatch/aw-webui. TopGit phản chiếu số sao của GitHub nhưng không cam kết đến từng phút.
ActivityWatch/aw-webui có những chủ đề gì?
GitHub topics của ActivityWatch/aw-webui: "activitywatch", "vue", "webui". TopGit xếp repo vào nhóm Frontend.
ActivityWatch/aw-webui còn đang phát triển không?
Commit gần nhất trên ActivityWatch/aw-webui là 9 ngày trước (theo timestamp GitHub). Repo có 198 fork — một chỉ báo về mức độ quan tâm của cộng đồng.
ActivityWatch/aw-webui là gì?
ActivityWatch/aw-webui (ActivityWatch/aw-webui) là dự án TypeScript trên GitHub. Theo mô tả gốc: Webapp for visualizing and browsing ActivityWatch data, built with Vue.js.
ActivityWatch/aw-webui so với các dự án Frontend khác thế nào?
ActivityWatch/aw-webui được TopGit xếp vào nhóm Frontend, với 155 sao GitHub và viết bằng TypeScript. Xem trang chủ đề Frontend trên TopGit để so sánh với các dự án tương tự theo số sao và mức độ hoạt động.
ActivityWatch/aw-webui viết bằng ngôn ngữ gì?
ActivityWatch/aw-webui chủ yếu viết bằng TypeScript. Trường "language" của GitHub dựa trên phần lớn byte ở nhánh mặc định.
Vì sao ActivityWatch/aw-webui được xếp vào nhóm Frontend?
TopGit xếp ActivityWatch/aw-webui vào nhóm Frontend dựa trên GitHub topics và mô tả của repo (gắn thẻ: "activitywatch", "vue", "webui"). Việc phân loại dựa trên metadata thật của repo, không phải đoán theo cảm tính biên tập.
Đọc đầy đủ README ở tab phía trên.
Muốn nghe thêm một ý kiến về aw-webui?
Hỏi một AI đọc được trang này — một cú bấm là có ngay nhận định về aw-webui.