Just curious, was something like https://github.com/containerd/stargz-snapshotter considered/evaluated before designing your own lazily-loaded container FS and if so, any pros/cons for the same?
Visa/MasterCard/Amex already support such a facility in India due to RBI requirements. Doesn't seem too difficult to adapt similar functionality for other countries too, if the regulations are updated to require it.
> The sqlite3 C API serializes all operations (even reads) within a single process. You can parallelize reads to the database but only by having multiple processes, in which case one process being blocked doesn't affect the other processes anyways. In other words, because sqlite3 serializes everything, doing things asynchronously won't speed up database access within a process. It would only free up time for your app to do other things (like HTTP requests to other servers). Unfortunately, the overhead imposed on sqlite3 to serialize asynchronous operations is quite high, making it disadvantageous 95% of the time.
> Thruster also wraps the Puma process so that you can use it without managing multiple processes yourself. This is particularly useful when running in a containerized environment, where you typically won't have a process manager available to coordinate the processes. Instead you can use Thruster as your CMD, and it will manage Puma for you.
You have Lidarr[1] as an equivalent to Sonarr/Radarr etc. and there is a pending PR[2] for adding Lidarr support to Overseerr which also has a custom docker image to try.
> When the value of auto-vacuum is 2 or "incremental" then the additional information needed to do auto-vacuuming is stored in the database file but auto-vacuuming does not occur automatically at each commit as it does with auto_vacuum=full. In incremental mode, the separate incremental_vacuum pragma must be invoked to cause the auto-vacuum to occur.
You have already gotten excellent options from the other comments, but here's another one that's not been mentioned yet.
You may want to consider adjusting your partition key (if feasible) as a function of datetime so you can just drop a complete partition when required, rather than needing separate delete queries.
In my experience, it has proven to be a very quick and clean way to clear out older data.
Eweka hasn't come up for renewal this year yet but the last year, I had to cancel my sub and set it up again due to the renewal issues. You may want to try doing the same since their BF promo is valid year-round: https://www.eweka.nl/en/landing/unlimited-usenet-special
Newshosting was the one that got renewed a few days and it went through fine without any manual intervention.
FWIW, I haven't had any failures in ~3-4 months now. Every subscription using Stripe has been working flawlessly for the same time. Even usenet subs have renewed fine this year (just had an automatic renewal processed yesterday).
I use ICICI, Axis & HDFC Cards and all 3 have worked fine.
If you care about permissions, you can always run an rsync after rclone has finished the transfer because applying just the permissions is much faster than the actual single-threaded transfers of rsync.