

along with the compose.yaml file, unless I need it in a different drive for any reason


along with the compose.yaml file, unless I need it in a different drive for any reason
btw, the prices of managed runners are going down, not increasing
https://docs.github.com/en/billing/reference/actions-runner-pricing#standard-github-hosted-runners
still good to have a self-hosted alternative though
ah right, my bad
fwiw, you can self host a GitHub actions runner


maybe they resumed development then, it was removed from Ubuntu and RHEL repos about 5 years ago when I had to look for an alternative


are you using a maintained alternative? Distros started to remove it from their repos years ago because it was not maintained anymore afaik


I’m the only user of my setup, but I configure docker compose stacks, use configs as bind mounts, and track everything in a git repo synchronized every now and then.


check you SSH_ASKPASS and SSH_ASKPASS_REQUIRE variables


deleted by creator


def possible, cloudflare DDoS their own dashboard a few months ago with some react code
https://blog.cloudflare.com/deep-dive-into-cloudflares-sept-12-dashboard-and-api-outage/


the standard was written in pounds, but the ass sitting was in stone
/anything but metric/
thanks, I had to restart to see the change. Why is a “text color” being used as background though
definitely doesn’t look as good as the GTK did, but I hope they simplify the interface at some point There’s no reason to keep these 3 menu areas, just bundle them together in tabs or one side menu to keep the hierarchy of players and effects under output/input.

edit: it’s actually 4 areas counting the preferences at the top right
mine has this brown color in some places and idk where I could change it in the KDE theme/settings



I think you need something like restic with a retention policy
https://restic.readthedocs.io/en/stable/060_forget.html#removing-snapshots-according-to-a-policy
--keep-{hourly,daily,weekly,monthly,yearly}
other solutions that implement similar policies are kopia and rustic
the advantage of using an off the shelf solution is that it’s almost certainly more reliable than what anyone can come up with in a few hours, and, it works with incremental backups, so your space requirements are drastically reduced depending how often you run it.


turns out it’s really easy to turn a profit when you don’t need to pay scientists and reviewers that create the content you’re selling
I’m actually surprised it’s not closer to 100%.


Intel has some GPUs that are more cost effective than NVIDIA’s when it comes to VRAM.
Arc A770 is selling for $370 in the US, and the new B50 for $399, both with 16GB.
B60 has 24GB, but I’m not sure where to find it.


should have done it in swedish to confuse most people


yeah, MPV is the goat
that is fine, the only requirement AFAIK is the user being in the docker group in case you’re having permission issues running it as user