• 3 Posts
  • 34 Comments
Joined 1 year ago
cake
Cake day: June 27th, 2023

help-circle

  • tko@tkohhh.socialOPtoLemmy Support@lemmy.ml0.19.4 Prerequisites
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    4 days 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









  • because it’s much, much faster and easier to consume content via video

    That totally depends on the content. Using your example, yes, a video of an explosion is going be much more efficient than a block of text about the same explosion. But for something like this, I find it MUCH slower to try to glean the relevant information from a video than from an article. An article can be skimmed easily so I only have to focus on the parts that I care about. Skimming a video, on the other hand, is a pain. Also, if the content is a step-by-step how-to, the video might be OK as long as I can follow along in real time. However, if I have to keep pausing and going back to rewatch a section, then an article is going to be easier to work with.












  • tko@tkohhh.socialOPtoLemmy Support@lemmy.mlReport Function?
    link
    fedilink
    English
    arrow-up
    9
    ·
    edit-2
    11 months ago

    I got this comment on another thread that answers my question:

    @Gaywallet@beehaw.org

    The following people get a report when content is reported:

    The community of the reported content

    The instance administrator for the community of the reported content

    The instance administrator for the person who reported the content

    The instance administrator for the person who was reported

    This makes my queue a mess at times, especially because federation is not instant and many apps cache content. I’ve had people on Beehaw report content on Beehaw that was already removed hours ago. When someone spams a bunch of content across communities on the fediverse (such as today with a prolific spammer) we can sometimes have dozens of reports for the same user because of all the reports generated above.