I never planned to create a “suite” of apps, but they got created one by one and then all of a sudden there was enough to call them all a part of a suite.
Before it started: The hkjc.uk domain
Before the initiation of development, I already owned the hkjc.uk domain and was already utilising it for my previous works, such as TimoETA and TimoJournal.
How it started: TimoServer
So TimoServer is not part of TimoSuite, but it is the foundation that TimoSuite builds upon. TimoServer is not a proper server, but rather converted from an old PC. This PC is an AIO (All-in-one) PC that was the trend when Windows 8 came out, meaning that the components sit behind the built-in touchscreen and are laptop grade. It had a 5th generation Intel Core i5, integrated graphics, 1 TB of storage (allegedly) and 4 GB of RAM.
Obviously, this was not going to be a server in that state, but it is not far from being capable of being my server. So I did two modifications:
installing Linux: I loaded Debian 13 for its reliability and relative ease to set up
upgrading RAM: I got 16 GB, which is basically the max that I can still find online considering the limitations with finding DDR3 SO-DIMM RAM
Managing the server: I installed Cockpit on the server, allowing for access to the server terminal from a browser in the same LAN. Using the hkjc.uk domain, I allowed access to Cockpit from anywhere in the world. Alternatively, I also set up SSH in the same way such that both a local IP can be used as well as a domain name.
TimoDrive: Cloud Storage
TimoDrive is the deployment of Nextcloud on TimoServer. This allows for cloud storage for cheaper than existing options, such as iCloud, Google Drive and OneDrive.
TimoOffice: Document Editing
TimoOffice is a feature in TimoDrive that provides an alternative to existing workspace solutions such as Microsoft 365 and Google Workspace.
TimoForums: Online Communications
TimoForums is a online forums platform that also includes AI, which is a feature not all mainstream forums platforms have.
Future Development
The possibilities of things that can be deployed on TimoServer are limitless. For example, I plan to host Git on this, so that code projects can be easily managed. Anyway, at some point TimoServer will not meet the power demand and I will need to build another server, but that is for another time.