I have a similar setup in my home office, where I have a floor standing desk lamp with a reflector to direct the light that I have pointed straight at the wall for indirect lighting.
Docker compose files (and docker execs) use the following format
yaml
volumes:
- <host_storage_path>:<vm_mount_path>
If the docker-compose has a ${VAR_NAME}:/data, then it will replace it directly with the variable defined in the .env file in the same directory with the format
I’m actually not sure you’re right… isn’t the metaphor a horse wearing a bridle with a bit in their mouth? When they’re excited to move they literally chomp on the bit.
If both h264 and hevc are stuttering using hardware decoding, something might be wrong. Try setting up Apollo or sunshine on your remote PC, and add Moonlight to your deck using the desktop App Store.
There are lots of guides online for how to install Moonlight and add it to your deck’s games list.
If that works smoothly with hardware decoding, then the problem is with remote play.
I wrote out the rest of this before rereading your post and want to put it out there for others:
If you’re having issues with hevc, switch back to h264.
Hevc is more computationally complex to encode/decode, so if you’re trying to do either with software, then it would be better to use the less compressed h264.
Network congestion over WiFi, as you pointed out, is often also a culprit.
What is your domicile like? An apartment with lots of nearby apartments? Freestanding house? WiFi congestion gets worse with more people using it.
If you have a dock, plug in an Ethernet cable to the dock and try streaming that way. Does it mitigate your stutter?
If so, turn down the bandwidth as much as you can and check (e.g 720p at 30 fps).
If it is that, buying a higher quality wifi access point may help.
Honestly, those are the most interesting builds to me. As an American, I’m waiting for tariffs to die before buying stuff of AliExpress, but one can hope.
They made it so server owners need a plex pass to stream to anyone outside the same LAN. Or the clients need to pay $2 a month if the server owner doesn’t have one
OnlyOffice local editors is probably the best drop in replacement for Microsoft office’s basic suite I have found. I’m a professional Linux user stuck in a company that depends on Microsoft products.
Doesn’t cover email, but is very good for everything else.
Can also edit PDF files, sort of. Doesn’t always format well on conversion from PDF to editable, but still workable in some cases
That’s definitely part of it. Also not an expert, but I believe you have the gist of it. Diesel engines are more efficient for a couple of reasons, not the least of which is more efficient heat capture to use for Work.
Another factor would be that if you want to do an oil combustion into steam power, you have a few issues:
You now have to lug around a LOT of both fuel and water, instead of just water and dry coal. Water and oil are both heavy by comparison to coal when lugging a train car of it around.
you now have two areas for heat loss to happen. Steam engines require massive boilers, high heat, and run much greater worst case failure risks (I.e. explosions) which are at highest risk when the water runs out. Coal is worse for this than I imagine oil would be, though inertia is a powerful force. Why move to another complicated system that does the same thing when you can use the old one?
Supply lines and training: if coal is already managed logistically, why switch to something else that provides a marginal benefit when coal is both cheap, easily accessed, and your engineers already know how to use it?
I’m sure there are even better reasons out there, but that’s what comes off the top of my head.
This is exactly what I would suggest, with one addendum: use internet archive links wherever possible. Especially if the links are intended to be clickable.
In the process of acquiring an advanced degree, I learned the worst part of research is finding dead links to pages that were never archived.
By putting it in the internet archive to create a link, it also adds a snapshot.
Also, if you do it right, I’m pretty sure you can cross-link your git repo’s markdown files without using the built in wiki.
This makes it a lot more portable if you want to update the wiki in your favorite text editor.