It is kinda weird that they have to take the entire site down at once to do maintenance. It still is spread across multiple servers, so why couldn’t it be rolled out in a way that only the smallest possible fraction is down at a time?
with db migrations the database structure changes. it’s not possible to do db schema migrations without downtime unless the application has been built with that in mind and the application is able to run with a partially upgraded schema.
Maybe they don’t want to complicate things trying to go with 0 downtime? Even though depending on how proper their infra is that might not be that hard.
It is kinda weird that they have to take the entire site down at once to do maintenance. It still is spread across multiple servers, so why couldn’t it be rolled out in a way that only the smallest possible fraction is down at a time?
with db migrations the database structure changes. it’s not possible to do db schema migrations without downtime unless the application has been built with that in mind and the application is able to run with a partially upgraded schema.
The Lemmy docs do go cover a bit on rolling releases, but it’s not recommended for large jumps or any upgrade that involves a database migration
Maybe they don’t want to complicate things trying to go with 0 downtime? Even though depending on how proper their infra is that might not be that hard.