Spyke

Replies

Comment on

A way to host Uptime Kuma

Reply in thread

I run netdata to collect usage statistics etc. directly on my VPS. I don’t need Uptime Kuma for that, because of course I know right away if my server is down or if it’s just a service. I am hosting some things also for my friends and family, and I’d like to have an option for them to check what is going on. Imagine they cannot access a service, they go to the status page and see that it is either a planned maintenance (updating, editing the configuration etc.) or there something else wrong, and they will see exactly when the service went back online. Without externally hosted status page like this, all they would get is an error. This way is much nicer for the non-technical audience.

memes

Comment on

Soon, hopefully

I didn’t use Reddit during the “Golden era” before the changes and redesign, but I really love Lemmy, the simplicity and feel of community is great. I think I found my new internet home here

Comment on

And so it’s gone

I am super sad that this actually happened. I was hoping for some last minute change of heart (yeah, stupid, but it was just a shred of hope). Apollo, you will be dearly missed. Reddit and Steve, you can go fuck yourself. And Christian, thank you for all the work you put into making Reddit more fun to use. We will never forget you <3

Comment on

A few questions about selfhosting from a newbie

Reply in thread

Yeah, I love Caddy so much. I’ve only ever used Nginx before, and it was a pain to configure. With Caddy, it’s just a few lines, and the automatic HTTPS is very nice.

Thanks for the SSH port tip, I’ve disabled password auth on all my servers before and only used key auth, but I will move the port to something other for extra security.

Comment on

A way to host Uptime Kuma

Reply in thread

I would like to use something open source. For now, I use the free tier of cronitor.io for my two websites and 3 cron jobs, but with that the free tier is all used up and I will have a bunch more services I want to monitor too.

Comment on

A few questions about selfhosting from a newbie

Reply in thread

I immediately started with using docker-compose because I was playing with a “playground” server from my provider and I wanted to be able to move my setup to the “production” server after setting things up. It’s much easier than the long docker run commands some docs suggest.

One question about the UID and GID, I’ve run into some trouble because the official Caddy image runs as root, so I had to set php-fpm also as root because otherwise it was causing problem. So what do you suggest to do with all my containers (I do not mean Caddy and php right now)? Should I run everything as the same UID and GID, or every container with it’s own user?