As the sysadmin for GMass, I’ve always wanted an app that lets me log changes that I make to a server configuration or to code, but I’ve never found a logging app that was designed specifically with the sysadmin in mind.
I did, however, find a journaling app called Day One that is meant for india phone number material personal journaling but I’ve found that it works well for my sysadmin needs. The key feature that makes it better than using Notes, Notepad, Google Docs, Word, or any other app that lets you type stuff, is that its little icon sits in the Mac Menu Bar so that adding a new entry is as easy as clicking the icon, typing your stuff, and hitting a button.
Day One makes it easy for me to quickly log a change to a server.
No browser to fire up, no need to remember a URL, and no need to log in. Just a few clicks and I can log an entry. Every time I modify my web.config file, for example, or update the GMass Chrome extension files, I log an entry describing what I’ve done.
Day One changed its business model in 2018
In mid-2018, Day One changed its business model, from a paid app to a subscription service. I welcomed the change because I’ve come to depend on the app and found its prior business model flawed. Since Day One lets you sync your entries across multiple devices, that means there’s a server involved that pushes and pulls information, and servers require maintenance, so it was always a mystery as to how Bloom Built, the company behind Day One, funded the maintenance and programming of servers when only collecting a one-time fee for downloading its app and using its servers.
However, when I switched to the subscription service, one of my devices became out-of-sync with the others. I’m not sure why this happened, but I suspect it’s because when I originally purchased Day One, I had done so with my Apple ID of [email protected], and when I purchased the subscription service, my Apple ID had changed to [email protected]. The one machine that’s been out of sync with Day One for the last year still showed the user logged in as [email protected]. To make matters worse, I had been making new journal entries from all of my various devices, including the out-of-sync computer. This presented the frustrating problem of getting the out-of-sync computer back in sync and making sure that any entries that were on the out-of-sync computer were also on the in-sync devices (before I resolved this, they were not).