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.
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.
I'm joining the cosiest café on the web here at bsd.cafe and therefore, it's time for an #introduction ☕
I have many interest, most of which I'll talk about at my main gotosocial account @ruben I'm here to talk about BSD and other tech topics, but feel free to discuss anything else as well!
I also have a personal website @ https://kedara.eu where I #blog, tend a #DigitalGarden / #wiki and try to contribute to the #Indieweb #smallweb communities.
It's running on #FreeBSD with a #Caddy webserver. My main #gotosocial account also runs there in a #bastilleBSD jail, together with other #SelfHosted services.
Nice to meet you, have a great day! ✨
I'm joining the cosiest café on the web here at bsd.cafe and therefore, it's time for an #introduction ☕
I have many interest, most of which I'll talk about at my main gotosocial account @ruben I'm here to talk about BSD and other tech topics, but feel free to discuss anything else as well!
I also have a personal website @ https://kedara.eu where I #blog, tend a #DigitalGarden / #wiki and try to contribute to the #Indieweb #smallweb communities.
It's running on #FreeBSD with a #Caddy webserver. My main #gotosocial account also runs there in a #bastilleBSD jail, together with other #SelfHosted services.
Nice to meet you, have a great day! ✨
Booked an #OpenBSD instance @OpenBSDAms in Dec and finally put it to use serving static #Jekyll pages. Setting up #Caddy and Let's Encrypt was refreshingly easy, and the OpenBSD FAQ helped with package management. The only real hurdle was serving content on port 80 and 443. I'm solving that with pf redirecting traffic to Caddy at the moment.
Booked an #OpenBSD instance @OpenBSDAms in Dec and finally put it to use serving static #Jekyll pages. Setting up #Caddy and Let's Encrypt was refreshingly easy, and the OpenBSD FAQ helped with package management. The only real hurdle was serving content on port 80 and 443. I'm solving that with pf redirecting traffic to Caddy at the moment.
I think I just give up configuring Nginx and just stay with Nginx Proxy Manager. That would mean I can't configure everything through files but at least it works.
I have now spent 2 days trying to get Nginx to work and I managed to reverse proxy to my selfhosted services with valid SSL certificates created with a DNS challenge but when I try to access my services via the configured URL I get an "/desktop#/" appended to it and half the apps don't like that and won't work with that.
I wish I could use Caddy but the way modules are installed for it is so unnecessarily convoluted IMO compared to Nginx plugins which you can just install with your package manager instead of having to build it with the modules included for yourself (or creating your own Docker image) which makes maintaining it a PITA (and I need a module for Caddy because I need DNS challenge for SSL certificates because I don't want to open any ports on my server).
Rant over I think
#selfhosting #nginx #caddy #reverseproxy #rant #nginxproxymanager #dnschallenge
I think I just give up configuring Nginx and just stay with Nginx Proxy Manager. That would mean I can't configure everything through files but at least it works.
I have now spent 2 days trying to get Nginx to work and I managed to reverse proxy to my selfhosted services with valid SSL certificates created with a DNS challenge but when I try to access my services via the configured URL I get an "/desktop#/" appended to it and half the apps don't like that and won't work with that.
I wish I could use Caddy but the way modules are installed for it is so unnecessarily convoluted IMO compared to Nginx plugins which you can just install with your package manager instead of having to build it with the modules included for yourself (or creating your own Docker image) which makes maintaining it a PITA (and I need a module for Caddy because I need DNS challenge for SSL certificates because I don't want to open any ports on my server).
Rant over I think
#selfhosting #nginx #caddy #reverseproxy #rant #nginxproxymanager #dnschallenge
I host my own Phanpy but there's a feature in dev (automatically populate alt-text if it's embedded in images, yessss!!!) I really want. So, I finally setup a build container for @phanpy and a small script to extract out the static folder so I can continue serving it out via Caddy. I wrote a quick post about it, I'm sure there are better and more idiomatic ways of doing this, so advice is welcome.
I host my own Phanpy but there's a feature in dev (automatically populate alt-text if it's embedded in images, yessss!!!) I really want. So, I finally setup a build container for @phanpy and a small script to extract out the static folder so I can continue serving it out via Caddy. I wrote a quick post about it, I'm sure there are better and more idiomatic ways of doing this, so advice is welcome.
Made a minor update on https://caddy.ninja/ to include "spam_and_bot_block" section
(Also now hosted on Alpine Linux VPS running Caddy - how meta!)
Made a minor update on https://caddy.ninja/ to include "spam_and_bot_block" section
(Also now hosted on Alpine Linux VPS running Caddy - how meta!)
Upgrading to Iocaine 3, and got a persistent exit code 216 from Caddy. It seems that the iocaine.service must be started before caddy.service, which is not true of other services I reverse proxy with Caddy. Curious.
https://paste.rossabaker.com/ross/83475e4a1d1b4006b082453aefa93287
Just some initial memory comparisons between my two tiny VPS servers - one running httpd/relayd on OpenBSD, the other running Caddy on Alpine Linux:
OpenBSD: 99M / 464M
Alpine: 50M / 464M
Both instances are hosting 3-4 simple, static websites. Interesting stuff (to me at least!)
Just some initial memory comparisons between my two tiny VPS servers - one running httpd/relayd on OpenBSD, the other running Caddy on Alpine Linux:
OpenBSD: 99M / 464M
Alpine: 50M / 464M
Both instances are hosting 3-4 simple, static websites. Interesting stuff (to me at least!)