I think I’d like more engagement though to really commit. Be able to turn my head and see more of the scene. Stand up and view a slightly different angle.

All of the tech exists to make this possible, I just don’t know if filmmaking can work that into the mix.

I’d honestly be down to buy a VR headset if movies otherwise used them in some sort of universal format. Definitely not buying Samsung/Sony/Paramount/Meta VR bullshit though.

Handbrake or VLC. I’d honestly just learn the CLI to make this work better for your benefit though. Much simpler to do remotely if you want changes.

https://docs.datalust.co/docs/collecting-docker-container-logs

You have a formatting issue. Solve for that instead of just switching to something else hoping it will get better.

I’m not sure what you mean. You either need to post a lot more details and information about your setup, or you need to read and understand the Tailscale docs.

For all traffic. Tailscale ACLs deny by default. If you’ve never changed them, you need to do that.

You need to adjust your ACLs to allow traffic over Tailscale.

Lazy idiots

If the application supports an API of some sort, you could run OCR, then send them over API as converted input.

If the apps don’t support them, then no.

If the apps don’t support them, then no.

Lol. Free Speech guy!

If you don’t want to expose port 80 or 443, then just change the ports they are running on. Right now you’re mapping 80/443 in docker, so just change those numbers to something else if you don’t want to use them. The number on the right is the internal service port, and the left of the colon is the port you’re opening to proxy to the port on the left. Adding Caddy does exactly the same thing and serves no purpose except another layer of obfuscation you don’t need.

You’re missing the point of Caddy, and your ports are all wrong. You don’t need it if you’re already exposing ports via Docker to 80/443. Remove Caddy.

Run a livecd of whatever Linux distro you like, and get a USB drive. Store persistent files on the USB stick.

A solar cluster and whole house battery bank would do this for the majority of the day. You need to hook it into your AC circuit with microinverters, and then have a circuit switch to handoff power back and forth. You’d at least be sure to run off solar during the day.

You could probably use yours for the same, but you need that AC transfer circuit into your breakers. Never do anything like this without an electrician.

If you’re not using some sort of Domain mapping, then the use of the same mount by two different sharing services with different uids is going to break ownership. Doesn’t matter if it’s Synology or anything else.

NFSv4 domain mapping solves this by having the same domain configured in client and server. That’s probably your simplest option. From memory, I do believe Synology DOES set uid for whichever user is authenticated via SMB and NFS though, so are you using two different users for these mounts by chance?

If you don’t want to bother to setup LDAP or domain mapping, then just use SMB and that should solve the problem.

What’s the question?

People are absolute fucking suckers. Can’t fucking believe this.

If you’re not worried about the desktop’s age or ability, you can just expand the array by growing the volume with bigger drives.

You don’t want to run raid on a DAS unless it for some reason handles it’s own, and then you might as well just get a NAS.

If you’re simply looking for more disk slots, you could rebuild and transfer your array into another machine, but then you’re probably back to NAS being a cheaper option.