-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Read-only mode (for backups) #1736
Comments
very good idea 👍 |
I like the idea... but.... this is going to be a pain.
Also you need to make sure snapshotting of your DB is done without locking the table. Still good goal to have. But I fear a lot of obstacles on the way. |
Sure, but nothing that can't be solved. And it should be solved - instead of finding new excuses ;) |
I am now in a situation where I need to phase out an old installation because of machine, domain and context change. (It's a completely different setup for different purpose, so we're intentionally not moving it). Having read-only on the old setup would be a very handy thing to have. I would be totally comfortable with a hacked-up version. Even if logins broke, last-login wasn't updated, logging wouldn't work... things like that. That would be better than completely removing the old resource immediately. |
Since I only care about files in that installation, would it break much, if I just |
I'm in that same situation again, and I'm wondering again if I can just |
So far, nothing has broken catastrophically. If you don't hear from me again this will mean It just works as intended (or I got run over by a car). If Nextcloud breaks in unexpected places, I'll get back to this issue. Until then, this might be the easiest viable option. |
This does not guarantee that nothing is written to the DB. Also it will fail hard when somebody tries to upload something. So don't do this - it needs to be handled in the application logic. |
I assume no such mode has been implemented into the server yet? |
drawbacks:
Opinions on this @nickvergessen @karlitschek @LukasReschke @rullzer @icewind1991 @blizzz @schiessle ?
The text was updated successfully, but these errors were encountered: