1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
|
+++
title = "Should I self-host my site?"
author = ["Michał Sapka"]
date = 2024-09-08T21:07:00+02:00
categories = ["blog"]
draft = false
weight = 2001
image_dir = "blog/images"
image_max_width = 600
abstract = "A genius idea?!"
+++
Up until recently, I was sure that my upload is limited to 20MB.
I was wrong - it's 40MB, and (if Ubiquity is to believed), it's _stable_ 40MB.
Way more than my low-traffic sites need.
If we don't count the bots, it's a few dozen people every day.
As I wrote [recently](/blog/2024/desktop-nas/), I am thinking about getting a dedicated compute server.
Playing with Synology is effective, but it's no fun at all.
But then another idea came: I have an unused Raspberry PI4.
Sometimes my genius scares me.
This little fella is _way_ more than a FreeBSD server serving just this site needs.
This would lead to separating my sites even more, like
- _unix-history_ becomes unixhist.<domain>
- _brain-rot_ becomes brainrot.<domain>
I have to say, that just thinking about it makes me smile.
What's sexier than an elf princess's swo... self-hosted site?
And dedicating RPi would delay purchasing a full-blown thin-client PC, which would be "I have all the power now" moment.
This raises a few concerns:
- I have a dynamic IP. I can use a dynamic DNS service, but maybe a relayd on my current OpenBSD Amsterdam can be used?
- Can I be doxed? I mean, you could simply WHOIS me, so most likely not a risk?
- With all the bots out there which can kill any server, would I be DDOSed all the time?
- How do I start every sentence with "btw, I host my website in my living room".
It's already difficult enough to put Emacs and BSD there!
Hosting a website is infinitely less complex than doing it for E-mail, so it's as close to a cakewalk as it gets.
If you can help me with those questions, please do.
|