LIST
➜ ~ kubectl exec --stdin --tty nextcloud-848f5d757b-kvx7b -- /bin/bash root@nextcloud-848f5d757b-kvx7b:/# which occ /usr/bin/occ root@nextcloud-848f5d757b-kvx7b:/# occ files:scan -- sdfueneb Starting scan for user 1 out of 1 (sdfueneb) +———+——-+—–+———+———+——–+————–+ | Folders | Files | New | Updated | Removed | Errors | Elapsed time | +———+——-+—–+———+———+——–+————–+ | 4111 | 36454 | 0 | 20936 | 0 | 0 | 00:00:21 | +———+——-+—–+———+———+——–+————–+
https://helm.sh/docs/helm/helm_dependency/ helm dependency list helm dependency update https://helm.sh/docs/chart_template_guide/subcharts_and_globals/ ➜ ~ kubectl --namespace default port-forward homeserver-grafana-647cbd75c9-2k5bt 3000:3000 ➜ ~ kubectl --namespace default port-forward alertmanager-homeserver-kube-prometheus-alertmanager-0 9093:9093 ➜ ~ kubectl --namespace default port-forward alertmanager-homeserver-kube-prometheus-alertmanager-0 9094:9094 loki 3100/TCP, 9095/TCP, 7946/TCP ➜ ~ kubectl --namespace default port-forward homeserver-loki-0 3100:3100 ➜ ~ kubectl --namespace default port-forward homeserver-loki-0 9095:9095 ➜ ~ kubectl --namespace default port-forward homeserver-loki-0 7946:7946
home assistant deployed in k3s Ultimate Home Server tutorial https://jaygould.co.uk/2024-01-01-setting-up-home-assistant-kubernetes-k3s/ ( https://github.com/jaygould/home-assistant/tree/e1262e6a42d1f00e6ef018a49b2993a5c21a24ff ) linuxserver https://docs.linuxserver.io/images/docker-homeassistant/#supported-architectures home assistant + k3s + zigbee https://jaygould.co.uk/2024-01-12-integrating-zigbee2mqtt-with-home-assistant-k3s-cluster/ ( https://github.com/jaygould/home-assistant/tree/f57fdc9d6aad964ed776f270aaa1f8b1844021e3 )
Analysis kgp -> showing nginx crashbackoffloop kl nginx-7bf7bd99c5-cw8vl -> showing no DNS resolution https://stackoverflow.com/questions/73297599/coredns-running-status-but-not-become-ready kubectl run -it test-nginx-svc --image=nginx -- bash curl http://:8080 curl http://nginx-service:8080 cat /etc/resolv.conf kgpa -> showing coredns pod not up –> dns is not working delete coredns kubectl delete –namespace kube-system pod coredns-6799fbcd5-m5jq2 delete nginx (to trigger redeploy instead of waiting for the crashloopbackoff) kubectl delete pod nginx-7bf7bd99c5-cw8vl
I also use Moon+ Reader via OPDS on Kavita. Kavita also supports OPDS-PS which syncs book progress back to the server so that you can pick it up on a different device right where you left off. Moon+ doesn’t support this, however it can sync book progress to google drive (maybe dropbox too!?) So that you can pick up where you left off on a different device, so long as you use Moon+ on that device as well....
Strict reverse proxies¶ This image uses a self-signed certificate by default. This naturally means the scheme is https. If you are using a reverse proxy which validates certificates, you need to disable this check for the container. src: https://docs.linuxserver.io/FAQ/#strict-proxy ... server { listen 10.1.2.3:80; server_name 10.1.2.3 myproxy.mycompany.com; location / { proxy_pass https://backend.server.ip/; proxy_ssl_trusted_certificate /etc/nginx/sslcerts/backend.server.pem; proxy_ssl_verify off; ... other proxy settings } src: https://serverfault.com/questions/341023/nginx-as-reverse-proxy-with-upstream-ssl ignored for now: proxy_ssl_trusted_certificate hope it works without…
https://ultimatehomeserver.com/docs/getting-started/ssl Configure certbot example from UHS sudo /opt/certbot/bin/certbot certonly \ --dns-cloudflare \ --dns-cloudflare-credentials ~/.secrets/certbot/cloudflare.ini \ --dns-cloudflare-propagation-seconds 60 \ -d <your domain> -d *.<your domain> example from certbot-dns-cloudflare certbot certonly \ --dns-cloudflare \ --dns-cloudflare-credentials ~/.secrets/certbot/cloudflare.ini \ --dns-cloudflare-propagation-seconds 60 \ -d example.com example from certbot-dns-route53 certbot certonly \ --dns-route53 \ --dns-route53-propagation-seconds 30 \ -d example.com mine: sudo /opt/certbot/bin/certbot certonly \ --dns-route53 \ --dns-route53-propagation-seconds 60 \ -d hs.tjenwellens.eu \ -d *.hs.tjenwellens.eu tjen@homeserver:/$ sudo /opt/certbot/bin/certbot certonly \...
curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC="–disable traefik" sh -s - src: https://www.suse.com/support/kb/doc/?id=000020082
➜ .kube cat ~/.ssh/config Host home User xxx Hostname 192.168.1.yyy IdentityFile ~/.ssh/zzz ServerAliveCountMax 30 ServerAliveInterval 120
https://github.com/plexinc/pms-docker/tree/master/charts/plex-media-server ➜ helm git:(main) helm repo add plex https://raw.githubusercontent.com/plexinc/pms-docker/gh-pages "plex" already exists with the same configuration, skipping ➜ helm git:(main) helm show values plex/plex-media-server > values.yaml ➜ helm git:(main) helm upgrade --install plex plex/plex-media-server --values values.yaml Release "plex" does not exist. Installing it now. NAME: plex LAST DEPLOYED: Sat May 18 10:41:13 2024 NAMESPACE: default STATUS: deployed REVISION: 1 TEST SUITE: None NOTES: Thank you for installing plex-media-server. Your release is named plex....