AW-SERVER(1)

💖 aw-server — the manual page, but make it a group chat 💖

okay bestie, sit down, hydrate, because we're talking about aw-server ✨ — that's the manual page for aw-server version 0.14.0+18fb62e, and she is iconic. 🎀

---

🦋 NAME 🦋

aw-server — literally the manual page for aw-server 0.14.0+18fb62e. that's it, that's the name, she said what she said. 💅

---

🌸 SYNOPSIS 🌸

the whole vibe, in one line:

aw-server [OPTIONS]

no subcommands, no drama, just you, her, and a whole buffet of options. 🍓

---

✨ DESCRIPTION ✨

Rust server for ActivityWatch. 🦀💖

that's the whole description. short. efficient. main character energy. no cap.

---

👑 OPTIONS 👑

okay this is the part where she shows off. every single flag, no skips, no "you get the idea" — we're doing ALL of them. periodt. 🎀

• --profile <PROFILE> — pick a named instance profile, like "default", "testing", or "research". this is the queen that decides your isolated directory root (and also the legacy testing-filename fallback, iykyk). defaults to "testing" in debug builds, and "default" in release builds. 🫶
• --testing — run in testing mode. it's giving alias for --profile testing 💅
• --verbose — verbose output, aka she tells you EVERYTHING and honestly? we love a chatty queen. 🗣️
• --host <HOST> — the address to listen to. 💖
• --port <PORT> — the port to listen on. 🔥
• --dbpath <DBPATH> — path to the database override. also lowkey implies --no-legacy-import if no db is found. 👀
• -c, --config <CONFIG>` — path to a config file override. 🎀
• --webpath <WEBPATH> — path to a webui override. ✨
• --custom-static <CUSTOM_STATIC> — a mapping of custom static paths to serve, and the format is exactly this, don't freestyle it: watcher1=/path,watcher2=/path2 🌈
• --device-id <DEVICE_ID> — device ID override. yes, you get to pick your own name. main character behavior tbh. 👑
• --no-legacy-import — don't import from aw-server-python if no aw-server-rust db was found. the "we're not doing that today" flag. 🙈
• --import-legacy — explicitly (re-)run the legacy (Python aw-server) database import, even if this datastore was already initialized. use this when the automatic import did not run because aw-server-rust had already started once before (ActivityWatch/aw-server-rust#546), or when you want to pull in a legacy database with --dbpath set (which otherwise implies --no-legacy-import). and bestie, re-running is safe: already-imported events are skipped instead of duplicated. no double-posting, we don't do that here. 💜
• --legacy-dbpath <LEGACY_DBPATH> — override the path to the legacy aw-server (Python) database you're importing from. defaults to the standard <data-dir>/activitywatch/aw-server/peewee-sqlite.v2.db location. 📁
• -h, --help — print help. your little emergency pocket guide. 🧚
• -V, --version — print version. 🎀

---

💫 SEE ALSO 💫

the full documentation for aw-server is maintained as a Texinfo manual. so if info and aw-server are properly installed at your site, this command:

info aw-server

should give you access to the complete manual. fr fr, go read her. 📚💖

---

lowkey reminder bestie: everything above is exactly what the page says — i just gave it a personality. don't come for me if you skip a flag and it doesn't work, that's on the vibe check you failed. 😭💅

---

and that's the whole thing!! this was aw-server 0.14.0+18fb62e, dated October 2026 — thanks for scrolling all the way down, you're a real one 🫶✨ mwah, go run your server, slay 💖🌈⭐