Yeah, I have dainty thin wrists :(
adam
And this picture perfectly demonstrates why I'm stuck buying the (usually slightly worse) "S" versions of smart watches.
Very first line of the GitHub readme. As a support tool it's mostly useless, endless similar or identical questions answered differently or not at all and none of it indexed by search engines for use on the web.
It's an awful data silo / black hole that increases volunteer load.
allows it to make its tokamaks at only two percent of the volume of conventional tokamaks
Strap that into a tank, with - hear me out - legs, and we're golden.
Easily doable in docker using the network_mode: "service:VPN_CONTAINER"
configuration (assuming your VPN is running as a container)
The Punch Escrow is a great pulpy book along the same lines.
Spoiler
Company comes up with foolproof way to ensure zero transporter accidents. Don't tell everyone that they've just invented a suicide booth that triggers when receipt of the copy has been verified - till that part fails and the original walks out after the copy has. Cue corporate thriller coverup story.
This is a 2 and a half (almost) year old article. I figured Tim's thoughts on this were common knowledge at this point?
It's unfortunate that (at least on the Bluesky side) an attempt at following a person doesn't result in them getting a DM asking for that to be ok.
Which means following a person on Bluesky is not possible unless they've already opted in.
All I want to do is follow a couple of authors or content creators but none of them know what bridgy.fed is :(
I've not used dockge so it may be great but at least for this case portainer puts all the stack (docker-compose) files on disk. It's very easy to grab them if the app is unavailable.
I use a single Portainer service to manage 5 servers, 3 local and 2 VPS. I didn't have to relearn anything beyond my management tool of choice (compose, swarm, k8s etc)
Without a pet-tax image I'm not sure I can upvote.
With a small amount of effort and the use of https://github.com/nanos/FediFetcher and https://github.com/g3rv4/GetMoarFediverse you can mitigate basically all those issues. It's still not perfect by any means but it results in a perfectly usable single user instance.
The first populates the replies of the home timeline posts you see (as well as profiles of people it finds in those replies) and the second pulls down all the content from instances you select for your followed hashtags (choose mastodon.social and you can guarantee you'll see most all posts with those tags)
It's the multiple volumes that are throwing it.
You want to mount the drive at
/media/HDD1:/media
or something like that and configure Radarr to use/media/movies
and/media/downloads
as it's storage locations.Hardlinks only work on the same volume, which technically they are, but the environment inside the container has no way of knowing that.