Switched to self-hosted Forgejo already so now I’m just waiting for my dependencies to switch.
10 minutes ago my forgejo test failed because github returned a 502 for the home-manager repo •-•
For even more context: That means that 89% of the time all parts that make up github work without issue. 11% of the time at least one component has issues/downtime.
https://mrshu.github.io/github-statuses/ shows the breakdown, git push/pull operations for example have 98.98% uptime.
Also, DNS is now depricated and will be removed in the merge window after the ipv4 removal. This will fix 90% of all networking problems.
Use a VPN, it’s not ideal but it’s secure.
When does your Server actually pull the repo though?
Are you sure you don’t need the lube?
I have linkwarden set up for this.
On Android I share to the linkwarden app to save, on pc i use the Firefox addon.
Sure it’s fragmented but I’m already used to doing things different between mobile and pc anyways.
Pro tip: If you’re using openwrt or other managed network components don’t forget to automatically back those up too. I almost had to reset my openwrt router and having to reconfigure that from scratch sucks.
If logging is down and there’s no one around to log it, is it really down?
That won’t work in most cases, all https traffic isn’t cached unless you mitm https which is a bad idea and not worth it.
Only cache updates those are worth it and most have a caching server option.
Infrastructure diagram? No! In this homelab we refer to the infrastructure hyperdodecahedron.
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.
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.
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.
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.
To understand recursion, first you must understand terminal capitalism.
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;
}
}
I don’t know but try it: https://abrahamjuliot.github.io/creepjs
Look on the bright side, it’s only 3,5 days of downtime a year.
https://uptime.is/98.98