• 1 Post
  • 10 Comments
Joined 1 year ago
cake
Cake day: June 27th, 2023

help-circle


  • 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 hear you… it’s definitely not about one tasting better than others, but maybe more about the eating experience. I do think there’s a legitimate argument about how different pasta shapes encourage different pasta to sauce ratios, but at the end of the day it’s just the two elements coming together and the taste is what it is. We should all enjoy it the way we want to! I just wanted to explain why some people talk about certain sauces and certain pasta shapes “belonging” together.


  • It has everything to do with the consistency of the sauce and how well it sticks to the pasta. For example, spaghetti with a meat sauce isn’t a great choice because the meat won’t actually stick to the pasta and you’ll have to scoop up that meat “manually.” Better is pappardelle, which has a huge surface area that causes the meat to stick to the pasta.



  • tko@tkohhh.socialOPtoLemmy Support@lemmy.ml0.19.4 Prerequisites
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    5 months ago

    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

    1. edit the docker-compose.yml file and add a new volume to the postgres service that looks something like this: - ./volumes/miscfiles:/miscfiles
    2. docker-compose up -d postgres (this starts just the postgres service from the docker compose file)
    3. 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)
    4. docker-compose down
    5. mv ./volumes/postgres ./volumes/postgresBAK20240628 (move your existing postgres data to a new directory for backup purposes)
    6. mkdir ./volumes/postgres (re-create an empty postgres data folder. make sure the owner and permissions match the postgresBAK20240628 directory)
    7. edit the docker-compose.yml and update the postgres image tag to the new version
    8. docker-compose up -d postgres (you’ll now have a brand new postgres container running with the new version)
    9. 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.)
    10. docker-compose down

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

    1. docker-compose up -d

    Hopefully that helps anyone that might need it!

    edited to reflect the comment below