this post was submitted on 29 Jul 2023
7 points (100.0% liked)
Café
777 readers
1 users here now
Welcome to our virtual third place, The Café.
Come on in and make a new human connection over a cup of coffee (or Teh Tarik). This is a casual community, do whatever you want, share your oyen pics, your frustrations, and even organize a weekend picnic with the community. The world is your oyster.
Rules are simple, be kind and civil with each other. As with any other café, rude patrons will be kicked out.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
lemmy zip failed to upgrade and had to roll back 12 hours,
don't scare our admins 😱
monyet already has a dev instance, so they can import the db from the main instance there, and do the db migrations to see if that'll succeed.
precautionary measures can be taken on the dev instance so it doesn't attempt to federate with all the data from here.
i can think of (for testing out db migrations on the dev instance):
run
lemmy_serverwith the--disable-scheduled-taskscli flag, which will prevent background federation tasks from running (so federation events will only be triggered by actual interaction, like posting, voting, subscribing, and of course such things should not be done on the dev instance)if that's still not enough and we want to be extra sure the dev instance doesn't federate with data from over here, then just block outgoing http/https connections at the firewall while doing the db migrations try-out (also don't run lemmy-ui and just watch the docker logs for it to say migrations completed successfully)
i think the lemmy.zip admins said they're still trying to work out a way to spin a dev instance on a dedicated server, but monyet already has a dev instance, so the db migrations can be tried first to ensure safety.
My apologies.
it's alright 👌