Gotcha… as long as you understand that any device that receives that traffic can see exactly what’s in it! (no sarcasm intended at all… if you’re informed of the risk and OK with it, then all is well!)

What’s your reason for using HTTP? That seems like a really bad idea this day in age, ESPECIALLY if that’s something you’re going to make available on the internet.

A reverse proxy is basically a landing place that acts as a middle man between the client and the server. Most people set it up so that all traffic on 80 or 443 go to the reverse proxy, and then the reverse proxy gets the correct website based on the host header of the request.

If you are currently serving multiple websites on your server, then that means you are serving each website on a different port.

So, just make sure that the reverse proxy is serving on a port that is not used by your other sites. It will only respond on it’s own port, and it will only serve the site(s) that you have configured in the proxy.

You’ll be fine!

I’m pretty sure I saw a stat that the Niners are dead last in special teams.

Checking in late… Team is looking good so far! Maybe need to stiffen up the pass protection, but I’m happy so far! Go Niners!!

Losing to the Rams always sucks, and espeically since it put us below 500 on the season.

BUT, I gotta say that even with the injuries, I think our offense is fine. Bell needs to figure out how to hold on to the ball, and the line could stiffen up a bit. Outside of that, Purdy was excellent again, Mason is a workhorse, and Jennings was a bonafide rockstar.

Defensive penalties were killer throughout the whole game. I’m not sure what’s going on with that, but I hope they can pick up the discipline for the rest of the season.

Penalties.

This game is getting tense! Let’s score some points on this drive!

Jennings!

I think we’ve had enough flags for the whole game, so let’s hope we keep it clean from here out.

Alright, let’s bounce back in our first home game against the Rams this year. Go Niners!

Sorry I missed the game yesterday. Seems like by the time the Niners got in gear, it was too late. Vikings played a great game though, so it’s hard to be too upset losing, especially since it’s only the second game of the season.

On to the Rams in Levi’s south. Let’s goooooo!

Yeah Mason! He’s having a night!!

Ohhh Deebo has number one now… I was wondering why he was back there fielding the punt!

So psyched to be here with you all! Let’s go Niners!!

Looks like it’s going to be Mason’s time to shine. Can’t wait to see what the offense looks like!

I run a Nextcloud instance on my Unraid server.

Eh, what’s gonna happen is gonna happen regardless if I pay attention to it or not… I guess I just prefer not to worry about it!

Indeed. A wise wizard once said: “It is a curious thing, Harry, but perhaps those who are best suited to power are those who have never sought it.”

It was not a prediction of victory… it was a 71% chance of winning the electoral college. Said another way, they gave her a 29% chance of losing.

https://projects.fivethirtyeight.com/2016-election-forecast/

ahhhh yes, that makes perfect sense… thank you for pointing that out! Especially since I’m not good enough with vi to know how to bulk delete the first character in specific lines, I had to manually arrow and delete.

I successfully migrated postgres 15 to 16. I followed the general idea of the guide you posted, but I found it a little easier to do a slightly different process. Here’s what I did:

1. docker-compose down for the lemmy instance

2. edit the docker-compose.yml file and comment out all of the services except postgres. In addition, add a new volume to the postgres service that looks something like this: - ./volumes/miscfiles:/miscfiles

2. edit the docker-compose.yml file and add a new volume to the postgres service that looks something like this: - ./volumes/miscfiles:/miscfiles
3. docker-compose up -d postgres (this starts just the postgres service from the docker compose file)
4. docker exec -it [container name] pg_dumpall -U [username] -f /miscfiles/pgdumpall20240628 (I think this will work, but it’s not exactly what I did… rather, I ran docker exec -it [container name] bash, and then ran pgdumpall -U [username] -f /miscfiles/pgdumpall20240628. The end result is a dumpall file saved in the ./volumes/miscfiles directory on the host machine)
5. docker-compose down
6. mv ./volumes/postgres ./volumes/postgresBAK20240628 (move your existing postgres data to a new directory for backup purposes)
7. mkdir ./volumes/postgres (re-create an empty postgres data folder. make sure the owner and permissions match the postgresBAK20240628 directory)
8. edit the docker-compose.yml and update the postgres image tag to the new version
9. docker-compose up -d postgres (you’ll now have a brand new postgres container running with the new version)
10. docker-exec -it [container name] psql -U [username] -f /miscfiles/pgdumpall20240628 (again, I think this will work, but I bashed in and ran the command from within the container. This also allows you to watch the file execute all of the commands… I don’t know if it will do that if you run it from the host.)
11. docker-compose down

12. edit the docker-compose.yml and un-comment all of the other services that you commented out in step 2

13. docker-compose up -d

Hopefully that helps anyone that might need it!

edited to reflect the comment below