For our lower environments we use rsync like the author but skip the pipeline altogether. The servers have a watch script to restart when files are rsynced. We then have a local watch script that rsyncs on file changes.
Relatively instant deploy (2-5s) whenever a file is saved.
Sounds like one of my 10 alarms, all with different tones, to make sure I wake up. This one is Krypton on Android.
Good call on a simulated failure. When I first set it up, it was LVM/BTRFS or ZFS as my top choices. It was a coin toss at the time because I hadn't built this sort of setup before.
I use immutable nixos installs. Everything to redeploy my OS is tracked in git including most app configurations. The one exception are some GUI apps I'd have to do manually on reinstall.
I have a persistence volume for things like:
I have 30 days (or last 5 minimum) of system rollbacks using BTRFS volumes.
The personal files are backed up hourly to a local server which then backs up nightly to B2 Backblaze using rclone in an encrypted volume using my private keys. The local server has a mishmash of drives in a mirrored LVM setup. While it works well for having mixed drives, I'll warn I haven't had a drive failure yet so I'm not sure the difficulty of replacing a drive.
My phone uses the same flow with RoundSync (rclone + GUI).
Git repos are backed up in git.
Logs aren't backed up. I just persist them for debugging and don't want them lost after every reboot.
Caches/Games are persisted but not backed up. Nixos uses symlinks and BTRFS to be immutable. That paradigm doesn't work well for this case. The one exception is a couple game folders are part of my personal files. WoW plugin folder, EvE online layouts, etc.
I used to use Dropbox (with rclone to encrypt). It was $20/mo for 2Tb. It is cheaper on paper. I don't backup nearly that much. Backblaze started at $1/mo for what I use. I'm now up to $2/mo. It will be a few years before I need to clean up my backups for cost reasons.
The local server is a PC in a case with 8 drive bays plus some NVME drives for fast storage. It has a couple older drives and for the last couple years I typically buy a pair of drives on sale (black Friday, prime day, etc). I have a little over 30TB mirrored, so slightly over 60TB in total. NVME is not counted in that. One NVME is for the system, the others are a caching layer (monero node) or temp storage (transcoding as it also my media server).
I like the case, but if I were to do it again, I'd probably get a rack mountable case.
Peter tingle.
Take the red pill Neo and wake up.
Wakes up to all the injustices in the world.
Noooo Neo, not like that!!!
Could be VRAM which is likely shared with the system's RAM for an integrated GPU.
I don't follow Apple's architecture much and I suppose you'd have to have hardware accelerated transcoding on, so I could be full of shit.
I had similar issues on my NAS before I built a streaming box with a dedicated GPU.
I actually liked Falcon/Winter Soldier for the most part. Enjoyed the cast, it explored issues I care about from wealth inequality to racism and immigration.
Wonder how much of it is just bad writing for him? Altered Carbon season 2 was really meh that he led. Then I imagine the original actor in his place and realise I just didn't like the plot that much compared to season 1.
I can't think of anything he's been in though where he's nailed the role outside of Falcon/Winter Soldier, where I'll admit there was lots of supporting roles. Man's either cursed with D-list writers, or, as you mentioned, lacks the charisma to carry it.
Use the browsers inspector to see the computed sheet and visualize margins and padding. Also helps detect selectors that aren't quite right as you can see the selector stack.
Small and incremental changes. Test after each change.
Also using the inspector, you can adjust values to find to find the desired computed value. Useful for getting margins/padding pixel perfect.
Break it down. Widgets are ideally reactive to the parent container. Layout is done separate and should be maintained without any widgets.
Be aware of selector precedence. This is why the inspector is helpful. You may need to use something like !important to deal with precedence.
If you are doing a lot with absolutes and relatives (e.g., menus), maybe look at the z-attribute to define how layers should overlap.
For the networking I found some repos with Nix and Gluetun (OCI containers). I don't see them in my bookmarks, so it was probably a day project when I set up and didn't keep the references.
That part is still in docker / podman. So any docker network guide just needs to be translated to nix.
Best resource I've found is searching GitHub.
My setup closely follows https://github.com/Misterio77/nix-config.
For servarr I just translated someone else's docker compose setup to nix. There are some ready made nix ones you can look at like https://github.com/rasmus-kirk/nixarr/tree/main/nixarr.
The complex networking I just picked up over time once I knew my way around a little bit.
GitHub is your best resource. lang:nix search terms.
The original used XI where it was 9 or 11 depending on the side.
edit: Nope I was wrong. That post links this one, lol.
https://infosec.pub/post/19153879