After my last update about my blog migration, basically all I did was install LiteSpeed Cache plugin and mess around with it.

For reference, lots of documentation goodness here

The most important part to note is that I kept getting bugged by both Google’s PageSpeed Insights and GTmetrix to enable text compression.

After some time reading about compression and Marco Saric’s post, I tried to enable compression by adding some lines of code at the bottom of the .htaccess file (accessible by the plugin through: LiteSpeed Cache->Toolbox->Edit .htaccess ):

<ifModule mod_gzip.c>
mod_gzip_on Yes
mod_gzip_dechunk Yes
mod_gzip_item_include file .(html?|txt|css|js|php|pl)$
mod_gzip_item_include handler ^cgi-script$
mod_gzip_item_include mime ^text/.*
mod_gzip_item_include mime ^application/x-javascript.*
mod_gzip_item_exclude mime ^image/.*
mod_gzip_item_exclude rspheader ^Content-Encoding:.*gzip.*

This didn’t work and realized that gzip doesn’t come enabled by default (most things were commented out) in yunohost’s nginx installation. So I referred to this link and edited the file /etc/nginx/nginx.conf :

gzip on;

add_header Content-Encoding "gzip2";
gzip_vary on;
gzip_proxied any;
gzip_comp_level 6;
gzip_buffers 16 8k;
gzip_http_version 1.1;
gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript

The line

add_header Content-Encoding "gzip2";

is the most important, after that my blog was tested for compression using: and , both test websites see compression enabled.

I’m still not sure about Google’s PageSpeed Insights but GTmetrix sees it as well. Here are my results (for now):

Google’s PageSpeed Insights

Just for fun (haven’t looked too much into this yet) I am adding the score for Website carbon as well:

So far I am more or less happy with the results and there is room for improvement. Some settings seem to break my Indieweb and ActivityPub plugins.

Day 15 of

I will try to make this entry resemble a tutorial, hopefully this ends up being useful to someone.

Why start over?

I had been playing around with Open Media Vault before (see this entry for details), but it was mainly based on docker images and I could never get Nextcloud up and running (the closest I came was installing nextcloudpi, but I could never get the docker image to run using external storage).

Also I never got to the part of using letsencrypt to access everything through https, pretty sure there’s a tutorial out there somewhere.

Then tragedy happened, for some reason my SD card just died and I was left with nothing.

After that I decided that my setup needed some improvements, and to be completely honest I also wanted to try something different, in yunohost almost everything is a one-click step when it comes to installing apps so that was a huge point in favor, here I am telling you my story:

Initial setup

After the SD card incident, booting from an external drive seemed like the best option. There are 2 prerequisites for that to happen:

  1. update the pi’s bootloader in eeprom (detailed steps here, see section: Update the bootloader)
  2. burn the OS image to the external drive, and use your favorite file browser to copy & replace some files to the boot partition (no need to do this if you’re using 64 bit Raspbian OS). This is the list of files that need to be replaces (just get them from the repo):
    • fixup.dat
    • fixup4.dat
    • fixup4cd.dat
    • fixup4db.dat
    • fixup4x.dat
    • fixup_cd.dat
    • fixup_db.dat
    • fixup_x.dat
    • start.elf
    • start4.elf
    • start4cd.elf
    • start4db.elf
    • start4x.elf
    • start_cd.elf
    • start_db.elf
    • start_x.elf

In my particular case the base was Raspberry Pi OS lite, I know, you may be thinking: “Aren’t there yunohost images already out there? save yourself some trouble!” and my answer is documented here.
Then after updating, it’s possible to install yunohost (4.0.3 at the time of writing) with a curl one liner: curl | bash

Post intsall steps are pretty straightforward, here’s a link.

I ended up using a domain as it was graciously offered for free.

My multi-HDD setup

Note: What this section describes has to be done after yunohost is up and running in the system, I tried doing it the other way around and that caused my SATA HAT to stop working altogether, no HDDs were detected, fan stopped spinning and the little LCD display showed nothing

A while back I got an awesome RADXA Quad-SATA HAT that houses 4x1TB HDDs. It is not detected or working out of the box but the installation process is detailed here. So my system has 5 HDDs (4 in the SATA-HAT and the one I boot from connected one of the pi’s USB ports).

I also wanted to have some sense of security for my data so naturally I set up 2x RAID1 arrays (mdadm is your best friend, here’s a useful guide)

All this sounds very nice, doesn’t it? There’s always a catch: since the external drives are on the SATA HAT it is not possible to just edit fstab and auto-mount them on the system, there is a service associated with the SATA HAT that needs to be running to “see” the drives. My hacky solution for now is mounting the drives everytime I restart the system (yes, by hand, like a caveman).

App installing and configuration

Installing apps was surprisingly easy, Gitea, WordPress, Nextcloud and Piwigo are one clic installs except for Synapse, the fix is just installing from testing branch: sudo yunohost app install --debug

Since the apps are installed in the boot drive I decided to move or reference content to/from the other drives. My Nextcloud instance has access to the external storage so I’m able to “upload” pictures to my external drives. then I just made symlinks from /home/ to reference the album directories in the external drives. Here’s an useful link, also, hopefully you don’t screw up like me but here’s a link on how to remove symlinks. Hacky solution, yes, but it works.

So far my idea is to “upload” content to external storage through Nextcloud and follow the same approach (for blogposts, videos, etc …)

I am also testing communication through my Synapse instance (I can be found as and the Nextcloud Talk plugin with my folks back home.


Because what kind of engineer would I be if I was satisfied? Improvements:

  • I recently bought a domain from Namecheap, so I’ll be using that for my blog in the future
  • Deciding between Writefreely or WordPress to migrate this blog (writefreely has federation and I don’t know if the activity pub plugin for wordpress is mature enough)
  • There is a problem with outgoing port 25 so my self-hosted email address can receive but not send any emails and there’s an issue with reverse DNS so basically even if I could send them they’d be rejected or best case sent to spam. Apparently this is a router issue, my ISP has replied that they don’t block anything on their side
  • Deciding if I move my inner circle from Signal to Element (through my Synapse instance) or just use Nextcloud Talk

Well, that’s all, any suggestions are greatly appreciated.

Day 10 of

Ever since I started looking into the Fediverse, FOSS/FLOSS, privacy and self-hosting I was pleasantly surprised by how engaging and helpful the community can be.

As an example: in Fosstodon all my interactions have been very nice, from sharing random unrelated stuff to asking for advice on more technical matters everyone has always been helpful and willing to give advice.

Another great experience I had recently was related with the yunohost project (long story short, my Open Media Vault setup went down in flames, tutorial coming shortly), being kind of a big project one would think that as an individual, communication would be slow or hard, kind of like with companies as a consumer.

Surprisingly, all it took was a toot and a post on their forum to get up and running.

My first interaction was related to the fact that the available Raspberry pi image was neither the latest version (4.0.3 at the time of writing) nor booting on my pi, so after reading that the pi 4 was not supported officially and tooting about it I was surprised to receive a response from @yunohost prompting me to install on top of Raspberry Pi OS lite (it’ll always be Raspbian for me) using a curl one liner.

My second interaction, and after installing some apps, I came across another issue, the synapse (Matrix server) app installation failed and I wrote this post on the forum. I was surprised again to receive an answer in less than 24 hours! This time I just installed from the testing branch on their repo.

I have nothing but good things to say so far, and I will donate to the project, it is only fair and they are doing a great job.

Day 9 of

Ever since discovering the Fediverse and reading toots from awesome people in Fosstodon, a little idea started to take shape in my head: perhaps its not that hard to self host, there are tons of tutorials and resources out there…And I need some alternative to google photos to share albums with my family back home


After some research and settled for a RaspberryPi server/NAS, now, the purists will say that it is not the ideal platform to host but I think it is perfect to get started and learn the basics or as a hobby, then you can move on to the big boy fancy server hardware.

The first step was to choose the hardware, I settled for this kit because it provides a nice way to attach 2.5″ SATA drives:
Dual/Quad SATA HAT, top board HAT and metal case from Radxa

It was easy to assemble and the process was fun:
Step 1
Step 2


For the software related part, I decided to install the Raspbian lite image from downloads. And then on top of that OpenMediaVault 5 since there are a lot of tutorials on YouTube and it has a nice GUI. Installation guide

I was up and running after following some instructions in the Radxa Wiki. Ran into some trouble with the Top board hat not displaying any information and RAID because my 4 drives were not detected at first by Open Media Vault and had to set up RAID from terminal- This setup has 4 1Tb HDDs on 2 x RAID 1 configuration – Just remember that forums are your best friends 😉

Now, you can basically learn everything related to Open Media Vault from Techno Dad Life. After a few tutorials I had a piwigo photo gallery up and running, accessible from my local network.

Hosting over 4G?

For the access through the internet part, the not so fun part: it is a long story, but in a nutshell I have to access the internet using a 4G router because my landlord sucks. Anyway it was a bit of a nightmare, after setting up dynamic DNS on my router with noip and also setting up OpenVPN (a very nice feature to have on a router if you ask me) I discovered that neither accessing my local network through VPN nor port forwarding were working.

After tedious exchanges with my ISP/carrier (I am using an additional sim card linked to my phone’s data plan), calls to the store where I got my router from and even TP Link’s product support; some random hero from my ISP’s customer support call center said “Officially we don’t support third party routers, that being said I would suggest you change your APN setting to internet.public” and here I am now, a week after following that advice, sharing photos with my family back home through means I trust and manage myself.

I also installed Murmur (The Mumble server component) on the Raspberrypi 4 and was amazed by how easy it was to set up. My use case is having voice with friends while we play 0 A.D.

Day 4 of