

I don’t know anything about Talos but can you try it in a VM with a test disk? That should answer all your questions and show you possible pitfalls.


I don’t know anything about Talos but can you try it in a VM with a test disk? That should answer all your questions and show you possible pitfalls.


You get One(1) DDR5.


for a homelab I don’t think it’s feasible to fully review the source code of everything you install
Here’s what you can actually do:
Sure you wont always catch ai slop this way but you don’t need to read a line of code to at least be reasonably sure your arr stack won’t get to the family photos.


Don’t you mean: “How much speedtest?”


Windows snobs cant even run Windows on without a super giga 1000€ license for more than 16 Core CPUs
I’m not using Windows servers at home but if I did then a license wouldn’t be a factor when deciding what hardware to buy.


Technically, a copper wire is a battery that charges in (a very tiny fraction of ) seconds.


From the moment I understood the weakness of my flesh, it disgusted me. I craved the strength and certainty of steel. I aspired to the purity of the Blessed Machine. Your kind cling to your flesh, as though it will not decay and fail you. One day the crude biomass you call a temple will wither, and you will beg my kind to save you. But I am already saved, for the Machine is immortal… Even in death I serve the Omnissiah.


But only to protect the children™ of course


Launch multiple?


Here:
server {
listen 443 quic;
listen [::]:443 quic;
listen 443 ssl;
listen [::]:443 ssl;
server_name jellyfin.kitsuna.net;
http2 on;
http3 on;
quic_gso on;
tcp_nodelay on;
# You can increase the limit if your need to.
error_log /var/log/nginx/jellyfin.access.log;
# ssl on;
# ssl_certificate /etc/nginx/certificate.crt;
# ssl_certificate_key /etc/nginx/certificate.key;
# ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # don’t use SSLv3 ref: POODLE
ssl_certificate /etc/letsencrypt/live/kitsuna.net/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/kitsuna.net/privkey.pem;
# ssl_certificate_key /etc/letsencrypt/live/kitsuna.net/privkey.pem;
ssl_protocols TLSv1.2 TLSv1.3;
add_header Alt-Svc 'h3=":$server_port"; ma=86400';
add_header x-quic 'h3';
add_header Alt-Svc 'h3-29=":$server_port"';
location / {
proxy_pass http://10.159.4.12:8096/;
# proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forward-Proto http;
proxy_set_header X-Nginx-Proxy true;
}
}


Yeah, to quote the manual:
"[Unsafe Rust allows you to]
[…] The unsafe keyword only gives you access to these five features that are then not checked by the compiler for memory safety."


At least people aren’t buying at these high prices, wouldn’t want them to stay there after all.


It’s right in the name, Structured Qisualisation Language (SQL).


Works on android too.


No? Everyone who uses the bitwarden app or browser extention has a local copy of the database that is used for read operations. You can’t disable this so everyone who uses bitwarden can still use their passwords even if the server dies.


That’ll be 800€ and all change you own.
I have set up Tor secret services in the past to do this.
The service exposed the SSH port which could then be accessed from anywhere as long as you can connect to Tor.