

I was just about to query the context to see if this was in any way a “logical” answer and if so, to what extent the bot was baited as you put it, but yeah that doesn’t look great…
I was just about to query the context to see if this was in any way a “logical” answer and if so, to what extent the bot was baited as you put it, but yeah that doesn’t look great…
No doubt fiscal policies put this (and other) councils on the back foot, but it’s reductive to ignore that the thing that tipped them over the edge was bureaucratic incompetence combined with being fucked by the Oracle Corporation.
https://www.theregister.com/2023/09/05/birmingham_city_council_oracle/
Finally a proper vertical tabs option!
Personal preference ofc but after trying it on a whim I can’t go back.
I’ve had some luck with Ubuntu, I’ve made my “notes” public in case it’s of use to you!
I’d started with bootcamp (windows) to add another bootloader option then went from there. Most of my docs go from there.
This is a classic conundrum.
Containers and their volumes are supposed to be ephemeral (right?).
Yet we use them to run little apps where we configure settings etc in the app which we would like to “keep” - thus back up. Yes in a proper set up you would hook your container up to something that is not ephemeral like a database somewhere, but often we just want an app, see it’s got a self contained docker image, and just run it.
Whilst not in the spirit of things… I’ve tried using Borg backup however it just fails due to random permissions on the volumes.
I should spend more time looking into it but haven’t the time right now, could be the solution is specific to the app/container but the simplicity of just backing up a /volumes/* directory is soooo tempting…
Edit upon reflection, what about a sudo cron tab to zip volumes and set useful permissions on the zip. Then Borg to backup the zip. Borg (or at least vorta) can easily run scripts before/after and pass variables relating to the backup though.