Analytics, permissions and https
Putting the rss aggregator server on https⌗
I simply went with let’s Encrypt and followed certbot instruction. It crashed mid way, not able to parse my nginx configuration. Finding in which section to put the certificates was a bit troublesome, but I figured it out eventually. I went to use Nginx docs for it, which are well written. Before that, I would use Linode tutorialswhich are very nice too, but lack in explanations.
I lost some time because my firewall was not allowing 443 but this was quickly fixed with ufw allow 443
Fixing a write permission issue⌗
This concerns my rss aggregator project, available here.
I’m not sure I wrapped my head around go file permission yet. When I changed my code to use executable path to find the files to open and write, I actually broke my application.
Thanksfully I had logging in place and could see it was a write permission issue. I tried to fix it, but it seems it’s still failing today. I need to dig deeper. I could just change
permission manually, but I feel like I need to do it from the go code, as I would never ask user to modify permission on a file to use a file generated by the program. I’ll investigate where I did a mistake when I have some time.
EDIT: Just my cron job failing.
Putting analytics on my gaming blog⌗
I have a little gaming blog, hosted on netlify, where I am curious about the traffic. Of course this information is available for a fee but I don’t feel like paying for satisfying my curiosity. I decided to use Umami, which doesn’t track personal information of visitors (or at least claim to) and is lightweight (2kB).
I went to use the Docker version and got a bunch of issues mostly related to the path Umami use. After lot of struggle and skimming their closed github issue, I realised that you have to change the BASE_PATH environment variable AND rebuild the whole image for BASE_PATH to be used.
Finally I went to test it and realised that most add-blocker block the script. You can change another environment variable to escape the block by renaming the script, but that would be a jerk move so I won’t do that.