Timekeeper
A self hosted time management system with a full API, automations, notification system, lockdown mode on devices, web client, and Linux client. It is how I keep myself organized when working on projects and has been the case since it was built. It is a full microservice application written in: Go primarially for microservices, C++ on the GTK client, C on OS daemons, Rust on waybar extensions, JavaScript on the web frontend.
History on this project
I'm going to quote my readme for this project because it does a great job explaining why this exists:
I have always had a lot of unstructured work in my life which has not inherantly been an issue for me. But, it has encouraged me to put systems in place for tracking my time honestly for myself and for any employers. Having something in place forces me to make sure everything is done like it should for the day and stops me from working until the sun comes up the next morning (yes I have done that before, but it was wonderful bit of code).
In the past I have used some timetracking software, but most of these are heavilly geared towards billing as a freelancer or consultant and I found them all to lack some or all of the above: the fine grained control I wanted on an API, the ability to do analysis like I want, the ability to restrict activity on a system, privacy\self hosted, support for automations, or a simple UI. So being tired of the solutions available not matching my needs I opted to write my own.
I wanted a time tracking system that let's me lock myself out of my phone without resorting to a random app the locks during x hours of time and I wanted something would also lock me out of certain Linux applications. The reason is fairly simple, if the work is keeping my skills sharp and building projects the most productive option for myself is to simply lock myself out of distractions that to me are lower priority, but the only way to do that would be if I could control the API because otherwise I am depending on multiple software applications which do not communicate with each other or do so fairly limited.
Disclaimer\background everyone uses this API in the following manner has agreed to it and several have asked me. This same API also can do things like notify a partner when I'm working so that they don't walk into the den and start chatting then pause...think for a second and be like my bad are you working? This is a much simpler solution because a push notification automatically goes to their phone, they have an API they can poll (if they're an engineer), or I can do something low tech like light up a small sign with an IR burster. And honestly, it does miracles for relationships because it just clearly puts that info in front to say...hey I love you, but I'm working...I might be a second to repond to a text and maybe we can have that lengthy chat in a few hours?
I also don't like the idea of my time for personal projects that may not be public yet being stored on someone's servers that can leak. I have in the past run my own company and written software which I did not want public I was working on at the time. To me the risk of a leak and that dropping every personal project I am working on into the public eye or disclosing the exact hours I worked on them is a major reason to run my own system for this. And I don't the reality that if I loose an internet connection or the service goes offline then I can't log what I've been up to.
It's also hard when you use a hosted service to cleanly and securely do automations because functionally you have to figure out a way for service x to call back into your network or you have to poll the service (which often is not possible because a lot of these only give you a webhook). For example I want to turn off my monitors on my PC in the den if I am in the living room because I have 4 of them and they idle draw a fair amount of power (sleep is off due to issue on my Linux install). And it allows little things like for example there is a entity in home assistant that is updated with my working state that allows automations to trigger different paths if I am working or not (ex disable the automatic light controls in a room).
Having a system like this also gives you the option to analyze your work for patterns. For example...do I typically work at night or during the day? What projects do I spend the most time on? While I'm not personally doing this right now it is something that I have done in the past when I was using pen\paper or old time keeping software so even though it has been a few years since I did that it is entirely possible I opt to do it again.
As for the UI...all I wanted on every time keeping program UI was a start\stop and a way to see my time. Most threw a login page, a prompt for the project (which this does support, but its not a required field), and just generally felt extremely formal\cluttered as they were a solution being offered rather than a single program for a user. So that's what this is...a very simple web UI, GTK client, and waybar binary that just show the info, render it cleanly, and let you start\stop. And on the backend so it's not always on your mind are the automations themselves for homeassistant and things like letting people know you are working.
For more information
You can see the project linked on Github here.