Lemmy itself doesn't use disk storage, it just writes to a db. If the disk is full then that's a postgres issue, not a lemmy one. Lemmy might not even know the disk is full if the db is on a different machine.
Interesting that Lemmy server has no disk access (that in effect, it just uses inter-process communication). Apparently it is possible to query a DB for the available remaining space for wherever that DB lives.
So IMO it is still a Lemmy issue. In the event that Postgres cannot handle the query (which I have not checked), it is still a Lemmy issue because Lemmy should not choose a DB that cannot provide storage info.
That's a Microsoft sql server command....
Oof.. well, hopefully that was just a bad example. Hopefully a FOSS SQL server exists with the same capability.
Depends on dependencies, I'm not sure of how lemmy is setup but even in read only mode you need to write logs and auth calls.
That’s not an obstacle. It’s a matter of where to draw the line for switching to read-only mode. A good design would obviously switch to read-only (w.r.t. user ops) when there is still plenty of space for logs.
True, I'm a little bitter from coming into companies that do cloud just because and get themselves into issues like having one big partition that fills up and refuses to boot.
Bug reports 🐞on🐛any🦠software🪲
When a bug tracker is inside the exclusive walled-gardens of MS Github or Gitlab.com, and you cannot or will not enter, where do you file your bug report? Here, of course. This is a refuge where you can report bugs that are otherwise unreportable due to technical or ethical constraints.
⚠of course there are no guarantees it will be seen by anyone relevant. Hopefully some kind souls will volunteer to proxy the reports.
related communities in the decentralised free world:
!broken_software@lemmings.world