They're not unemployed or underemployed by any common definition of those words. If California wants to support striking workers, great, but it shouldn't be under these programs.
And realistically there's no reason why this isn't a Union problem to solve instead of a government one. Dues are paid for a reason.
https://xpenology.com/forum/topic/61634-dsm-7x-loaders-and-platforms/
There really is nothing close to Google Photos outside of Synology. And it's not 100% in terms of search but it's getting there.
You can run the Synology software via a loader on commodity hardware or on a hosting platform provided the platform supports VMWare ESXi or the like.
yes the whole nation is in jeopardy because some warmongers arent getting their promotions
The whole nation is in jeopardy because these leadership positions are being held open until Trump is reelected in a rework of the Merrick Garland SC nomination. Which should be terrifying. Jan 6 failed in part because some of the military top brass (Miley) put oath before Trump.
Read up on Project 2025 if you haven't. These "unconnected events" are anything but. It's a strategy.
Unless you make it a point to procure an LTSC version, which Microsoft won't even sell to you unless you have a site license.
LTSC is the only version of Windows that behaves like it's still your computer, and I have uptime measured in months on a computer who serves Plex all day long.
Honestly, don't bother with a dGPU and get a 12th or 13th gen Intel Core chip with QSV. Intel quietly tuned it up to the point where it's faster than nVidia's NVENC engine even in the latest gen plus you don't have mess around with the uncap streams hack and you're transcoding through system RAM not dGPU RAM, so far less likely that your stream limit will be artificially constrained by memory limitations.
To answer the question you asked though, the nVidia NVENC is the best solution on a dGPU. It's performance is largely the same across the same board generation, with one exception in the GTX 10X0 series. The absolute cheapest card you can lay your hands on that has an NVENC engine is the 1050TI.
The caveat is the 1070 and 1080 have two NVENC engines. It will double max number of streams in theory, however in reality you're memory bound on those cards and it's more like a 33% bump.
Good note, thanks. Just made the change.
Here we go:
Any place you see , you need to change it to fit and omit the <>. If something in two differet places like this, make sure they match when you're done as well. Specifically, the postgres user and password in the lemmy docker file and the lemmy.hjson.
Finally, in Google drive the files end in .txt so you can view them. You'll need to correct the file names when you download them if you intend to use them. You should have two docker-compose.yml, one in each of the two directories you create, and one lemmy.hjson.
From a fresh CLI Debian 11 install:
su
/sbin/usermod -aG sudo <user>
groups <user>
apt-get install sudo
cd /opt
mkdir npm
cd npm
(copy or create docker-compose.yml)
apt-get install docker-compose
docker-compose up -d
cd /opt
mkdir lemmy
cd lemmy
(copy or create docker-compose.yml and lemmy.hjson)
mkdir -p volumes/pictrs
chown -R 991:991 volumes/pictrs
docker-compose up -d
docker ps (verify containers are all running, grab ip address for lemmy container)
Configure port forwarding in npm for your lemmy container (npm should be accessible at debian_ip_address:81)
Remember to do the custom paths from the various guides. The lemmy port in this guide is 1234.
Please note I am not addressing federation or SSL or true hosting yet. I haven't got that far yet. But if you can get the damn thing running, the last mile shouldn't be too bad.
Here we go:
Any place you see , you need to change it to fit and omit the <>. If something in two differet places like this, make sure they match when you're done as well. Specifically, the postgres user and password in the lemmy docker file and the lemmy.hjson.
Finally, in Google drive the files end in .txt so you can view them. You'll need to correct the file names when you download them if you intend to use them. You should have two docker-compose.yml, one in each of the two directories you create, and one lemmy.hjson.
From a fresh CLI Debian 11 install:
su
/sbin/usermod -aG sudo <user>
groups <user>
apt-get install sudo
cd /opt
mkdir npm
cd npm
(copy or create docker-compose.yml)
apt-get install docker-compose
docker-compose up -d
cd /opt
mkdir lemmy
cd lemmy
(copy or create docker-compose.yml and lemmy.hjson)
mkdir -p volumes/pictrs
chown -R 991:991 volumes/pictrs
docker-compose up -d
docker ps (verify containers are all running, grab ip address for lemmy container)
Configure port forwarding in npm for your lemmy container (npm should be accessible at debian_ip_address:81)
Remember to do the custom paths from the various guides. The lemmy port in this guide is 1234.
Please note I am not addressing federation or SSL or true hosting yet. I haven't got that far yet. But if you can get the damn thing running, the last mile shouldn't be too bad.
So I wanted to make a top-level post: I've got a set of example files, and instructions, that will work 100% of the time on Debian. What do you guys think would be the best way to share them? A post here and the files shared on Google Drive? GitHub? Definitely open to suggestions, but I don't want anyone to struggle with it as hard as I have.
This worked for me, with one note:
and need to be lemmy and password if you're using the stock lemmy.hjson file, or the lemmy_lemmy_1 container will get stuck in a reboot loop. There's no define in the stock file in githubusercontent currently for those, so you have to add them by hand.
For security, you have to change these.
rm -rf /home/*
You need the directory for the mount point.