I brought back a few more sites by re-aiming DNS for my domains at an #AlmaLinux 9 VPS that runs the #Caddy web server and did some builds in #Hugo and #Zola, so now I'm also running:
https://passthejoe.net
https://zola.passthejoe.net
https://stevenrosenberg.net
https://wruby.passthejoe.net
I have been maintaining this VPS in terms of doing updates, but I didn't know I still had the web server running, and at least one of these domains was already aimed at it. Now all 4 are working.
I thought I would give up the server, but I like the ease with which I can add sites in Caddy, and it's been a very reliable environment. It's a low-RAM VPS -- 512 MB -- so I had to set up a swap file just to get it to dnf upgrade. There's enough RAM to run the web server, but it's no powerhouse.
The kind of immediate writing I did in that microblog -- which went to Mastodon anyway -- was easy because I used a script in the terminal is better done in a "real" microblog like snac2, but it's nice to have an archive of what I was thinking (and typing into my Ruby script).
I haven't done a programming project like it (https://github.com/passthejoe/blogPoster) ever since, and I should. I want to do something that's a desktop GUI, and programs that help me write and publish blog posts with less friction still have a lot of appeal.
The social media paradigm of "type into the box, hit send" is still pretty powerful. All the things you need to add to a post (title, tags, categories, images) just makes everything take longer, and in my case it makes me write less, or write fewer shorter posts. That's good or bad, I guess, depending on how you look at it.
I still think @bt@bsd.cafe has the right idea with his simpler static site blogging systems https://btxx.org/projects/
I brought back a few more sites by re-aiming DNS for my domains at an #AlmaLinux 9 VPS that runs the #Caddy web server and did some builds in #Hugo and #Zola, so now I'm also running:
https://passthejoe.net
https://zola.passthejoe.net
https://stevenrosenberg.net
https://wruby.passthejoe.net
I have been maintaining this VPS in terms of doing updates, but I didn't know I still had the web server running, and at least one of these domains was already aimed at it. Now all 4 are working.
I thought I would give up the server, but I like the ease with which I can add sites in Caddy, and it's been a very reliable environment. It's a low-RAM VPS -- 512 MB -- so I had to set up a swap file just to get it to dnf upgrade. There's enough RAM to run the web server, but it's no powerhouse.
Dear #mastoadmins, I'd like to improve the current setup using #caddy and #podman #compose. Is anyone using #podman #quadlet with #systemd? Also I understand that having the connection between caddy reverse proxy and mastodon via sockets is very cool and I'd like to give this a try as well.
Systemd is now offering keeping podman quadlet containers up to date by itself. Maybe this one can be leveraged as well.
Reverse proxy recommendation tier list for self-hosters:
S tier: Caddy (automatic HTTPS, simple config)
A tier: Traefik (Docker-native, label-based routing)
A tier: Nginx Proxy Manager (GUI-based, beginner-friendly)
B tier: Nginx (powerful but manual config)
C tier: HAProxy (enterprise-grade, complex config)
Caddy is the right choice for 80% of self-hosters. 3 lines of config for a fully working reverse proxy with automatic SSL.
#selfhosted #reverseproxy #caddy #traefik #nginx #docker #hom...
Reverse proxy recommendation tier list for self-hosters:
S tier: Caddy (automatic HTTPS, simple config)
A tier: Traefik (Docker-native, label-based routing)
A tier: Nginx Proxy Manager (GUI-based, beginner-friendly)
B tier: Nginx (powerful but manual config)
C tier: HAProxy (enterprise-grade, complex config)
Caddy is the right choice for 80% of self-hosters. 3 lines of config for a fully working reverse proxy with automatic SSL.
#selfhosted #reverseproxy #caddy #traefik #nginx #docker #hom...