Create installation methods for non-developersSee original GitHub issue
Right now you pretty much need to be a developer to start using ActivityWatch. (not anymore!)
One easy improvement we could make is to create a bash one-liner that installs ActivityWatch (much like the one-liner used to install brew). In the future (when we leave beta) we’d likely have to distribute installers/packages.
Would require some kind of process management for aw-server and watchers. (we now have aw-qt)
- Linux: Build a portable
- macOS: Build a portable
- Windows: Create a portable
May do (secondary goals):
- Make ActivityWatch start on login for all installation methods (when possible, have a checkbox for those who want to opt out). See #116.
- macOS: Build a macOS
.app(done, but issues remain)
- macOS: Create a homebrew formula. Done by @freayd, install using
brew cask install activitywatch.
- Linux/Debian: Build a
.deb(work in progress)
- Linux: Create an AppImage? (Wikipedia)
- Linux: Create a flatpak. See #476.
- Arch Linux: Create a PKGBUILD and upload to AUR (done)
- Windows: Create an installer using
NSIS or WiXInno Setup.
- Windows: Create a Chocolatey package (done: https://github.com/chocolatey/chocolatey-package-requests/issues/552)
- Put installation instructions in README
- Created 7 years ago
- Comments:35 (28 by maintainers)
Top GitHub Comments
@ErikBjare Please, make normal ActivityWatch deb packages and repository for Ubuntu and Debian systems, I can help you with this task, it’s not hard, see https://wiki.debian.org/Packaging/Intro The main task is to make correct Debian source package and only from this source package you can then build the Debian binary package which is what actually get installed. The source package consists, in its simplest form, of two things: The upstream tarball, renamed to follow a systematic pattern. A debian directory, with any changes made to upstream source, plus all the files created for the Debian package.
If you wanna make useful and correct debian packages then we should create separate packages for activitywatch-server (and maybe one more for activitywatch-server-rust), activitywatch-watchers, activitywatch-systray-qt. Each package should start his service (aw-server, aw-watcher-afk, aw-watcher-window, etc) in user-session either by having .desktop file in /etc/xdg/autostart or with systemd, see https://wiki.archlinux.org/index.php/Systemd/User and https://www.freedesktop.org/software/systemd/man/systemd.special.html#graphical-session.target systemd offers users the ability to manage services under the user’s control with a per-user systemd instance, enabling users to start, stop, enable, and disable their own units. This is convenient for daemons and other services that are commonly run for a single user, such as mpd
Only activitywatch-systray-qt package should depend on QT libraries and this package could depend or recommend activitywatch-server and activitywatch-watchers packages.
I can help you and take some tasks - please just create debian/control and debian/rules according to https://www.debian.org/doc/manuals/packaging-tutorial/packaging-tutorial.pdf#Outline0.2.3.15 (you can use dh-make command for this) for each package (activitywatch-server, activitywatch-watchers, activitywatch-systray-qt) or one debian/control and debian/rules file for all packages if you will always distribute all activitywatch components sources in one archive. I can do all other taks - compile and test deb packages, fix packaging issues, create PPA repository and write automated packaging building recipe from git, see for example https://code.launchpad.net/~gnome-shell-extensions/+recipe/gnome-shell-extensions-enhancements and https://help.launchpad.net/Packaging/SourceBuilds
Hi everyone. The brew formula is now available. You can install it with:
brew cask install activitywatch
Creating a .app would be a nice next step for macOS.