I have made too many projects in my lifetime, and thought that a repository is not enough to handle support for them. I also believe that to be able to dump my mind from time to time keeps myself on track. I make projects because I like to help people with problems that may or may not be an issue, now or in the future.
Deploy the site to the web server should be straightforward. However, there are a couple of hurdles to overcome to ensure that nothing goes wrong. In the end I found something that works for my scenario.
Creating the daemon infrastructure, managing the communication and refactoring the project into more complex, but far easier to handle application.
RPi4 was not able to properly play a video file, so an investigation was to be made, and the findings was satisfying.
Tinkering with my media machine, making hard decisions but getting everything working.
Trying to set up a Discord bot for my RSS feed, but problems arise, forcing me to implement a solution myself.
Dark mode have been added for those that feel like light mode is too bright for them. I myself prefer dark mode when I use my phone, but I chose to have both of them because some physically cannot read light text on dark backgrounds 1. It was not that hard either, as some may think that it involves JavaScript and user interaction, it is a standard for around 5 years 2.
Before I created this site I contemplated if I would do so at all. I have been using Discord for years, and it has been working fine. However, there are three reasons why I needed to move away from it. First being that Discord is a proprietary and centralized platform which can either become completely locked behind subscription or closed down at short time notice. Second is that while I invite only certain people to my server, I have heard some voiced opinion on invites from people I has of yet get to known close enough to feel comfortable to invite.
OpenSpeedTest is basically a speed test in your web browser you can run locally. It is used most commonly to verify the practical throughput from one host to another. Though, it is far from perfect, and you cannot use it for any host or service. For that it is better to use iperf3. But it works for any device having a web browser.
While using it I found two issues that made the result quite interesting and one weary on both client and server configs.
I mentioned over a year ago about the collection in Ansible I used for VyOS. I had some issues with it regarding differences and performance, so I had to resolve to some odd workaround which was ugly(clear config path and recreate from scratch, which was very slow on big configs), but quite easy to use directly with VyOS. I later on made some custom templates for it to reduce boilerplate and coupling.
A couple of days ago I found out by my teacher that they skipped the next round of opposition(I think that’s how you translate it), so I have to start all over in the next course starting next week. While they will be more strict this time around, needing to be more specific regarding the research question, I can still reuse most of my current work. Hopefully I can even finish writing earlier due to this, but I have no idea what the future holds.