Project

plugin: frontmatter-generator obsidian://show-plugin?id=frontmatter-generator config: { title: file.properties.title, ...file.properties, lastmod: file.properties.lastmod || file.properties.updated || file.properties.modified, date: file.properties.date || file.properties.created.split("T")[0], slug: file.properties.title.toLowerCase() .replaceAll(/[^a-zA-Z0-9]+/g, '-'), aliases: [...new Set([ file.basename, file.basename + '.md', ...(file.properties.aliases || []), ...(file.properties.slug ? [file.properties.slug] :[]), ])].filter(f => f !== file.properties.title.toLowerCase() .replaceAll(/[^a-zA-Z0-9]+/g, '-') ), }

(Initramfs): /dev/sda2 contains a file system with errors, check forced. Inodes that were a part of a corrupted orphan linked lost found. /dev/sda2 : UNEXPECTED INCONSISTENCY; RUN fsck manually.(I.e ., without -a or -p options). fsck exited with status code 4. The root filesystem on /dev/sda1 requires a manual fsck solution fsck -yf /dev/sda2 Src: https://askubuntu.com/questions/885062/root-file-system-requires-manual-fsck#885066

inspired by: https://github.com/milafrerichs/hugo-wikilinks copy relevant files from your template into matching folder cp themes/PaperMod/layouts/_default/single.html layouts/_default/single.html cp themes/PaperMod/layouts/_default/list.html layouts/_default/list.html change content rendering to use the wikilinks partial old: single.html ... {{- if .Content }} <div class="post-content"> {{- if not (.Param "disableAnchoredHeadings") }} {{- partial "anchored_headings.html" .Content -}} {{- else }}{{ .Content }}{{ end }} </div> {{- end }} ... new: single.html ... {{- if .Content }} <div class="post-content"> {{- if in ....

app service deployment db secret db config disable registration DISABLE_REGISTRATION db service deployment secret 1password config backup cron nginx http ssh -> failed could https://stackoverflow.com/questions/71789156/how-to-redirect-ssh-requests-in-nginx sudo mkdir -p /opt/gitea/tmp /data/gitea/gitea /opt/gitea/db-data /data/backups/gitea sudo chown tjen:tjen -R /opt/gitea /data/gitea /data/backups/gitea sudo find /opt/gitea -type d -exec sudo chmod 755 {} + sudo find /data/gitea -type d -exec sudo chmod 755 {} + sudo find /data/backups/gitea -type d -exec sudo chmod 755 {} + tree /{data,opt,data/backups}/gitea gitea ssh failure port forward straight to gitea 2224:22 worked port forward to nginx 2224:224 did not work (where nginx was stream{} configured to pass to gitea:22) for some reason, nmap on homeserver also did not show port 2224 open (earlier it did show 2222 open, when I was trying with that port…)

Explore cloudflare and svelte-kit

logs from nginx show [emerg] host not found in upstream plex in /etc/nginx/conf.d/ssl.conf others also show unable to find ip for service names reboot all failed kube-system stuff kgp -n kube-system kdelp ... troubleshoot dns stuff src: https://forums.rancher.com/t/k3s-dns-resolution-failure/39091 kubectl run -it --rm --restart=Never busybox --image=busybox:1.28 -- nslookup kubernetes.default for p in $(kubectl get pods --namespace=kube-system -l k8s-app=kube-dns -o name); do kubectl logs --namespace=kube-system $p; done fix coredns by rebooting it so coredns is having issues let’s reboot it...

I like Grafana/Loki/promtail etc. it just fits because i already use Grafana anyway for metrics/graphs and such. Datalust Seq is also nice, as well as Parseable/logstash/Grafana as a combo. Graylog can do a lot but its too bloated and too hungry for my taste (damn elasticsearch). Src: https://www.reddit.com/r/selfhosted/comments/17velmx/best_platform_for_selfhosted_logs/ Install grafana Install loki Install promtail on each node Configure Grafana Data Sources & Dashboard https://akyriako.medium.com/kubernetes-logging-with-grafana-loki-promtail-in-under-10-minutes-d2847d526f9e Promtail sidecar https://medium.com/@t-velmachos/deploy-promtail-as-a-sidecar-to-you-main-app-6182fa27db65 Promtail setups...

install 1password connect server https://developer.1password.com/docs/connect/get-started/?deploy=kubernetes&method=1password-com#manual-step-2-deploy-1password-connect-server Step 1: Create a Secrets Automation workflow https://my.1password.eu/developer-tools/directory create a connect server save 1password-credentials.json save connect token (skip) Step 2: Deploy 1Password Connect Server skip in favour of installing together with operator helm repo add 1password https://1password.github.io/connect-helm-charts/ helm install connect 1password/connect --set-file connect.credentials=1password-credentials.json Kubernetes Operator https://developer.1password.com/docs/k8s/k8s-operator/?deployment-type=helm helm repo add 1password https://1password.github.io/connect-helm-charts/ helm install connect 1password/connect --set-file connect.credentials=1password-credentials.json --set operator.create=true --set operator.token.value=OP_CONNECT_TOKEN usage 1password: vaults/pet....

copy to nextcloud rclone copy --progress ~/Downloads/google-photos-takeout/Takeout/Google\ Photos home:/data/nextcloud/sdfueneb/files/InstantUpload/google-photos-takeout --exclude ".DS_Store" --exclude "*.json"

sudo mkdir -p /opt/nextcloud-db/db-data /data/backups/nextcloud-db && sudo chown tjen:tjen -R /opt/nextcloud-db/db-data /data/backups/nextcloud-db && sudo find /opt/nextcloud-db -type d -exec sudo chmod 755 {} + && sudo find /data/backups/nextcloud-db -type d -exec sudo chmod 755 {} +