-
Install Homebrew The Missing Package Manager for macOS (or Linux) — Homebrew
-
Download Miniforge3
-
Install Miniforge3 and restart your terminal as soon as the installation finishes:
# Docker multistage build ghost blog with AWS S3 storage adapter | |
# Configure ghost-storage-adapter-s3 | |
# => https://www.npmjs.com/package/ghost-storage-adapter-s3 | |
# stage | |
FROM ghost:3.17-alpine as ghost-storage-adapter-s3 | |
WORKDIR $GHOST_INSTALL/current | |
RUN yarn add "[email protected]" | |
# build |
Beispieldateien für Traefik als Reverse-Proxy und Bitwarden als zu nutzender Dienst. Traefik nutzt die DNS-Challenge, um ein Wildcard-Zertifikat zu beantragen und um keinen Port im Heimnetzwerk nach außen öffnen zu müssen. In diesem Beispiel wird davon ausgegangen, dass Netcup als DNS-Provider genutzt wird.
Einträge mit sub.domain.tld
müssen mit der eigenen Domain ersetzt werden.
Alle Keys und Logins müssen ebenfalls mit den eigenen Daten ersetzt werden.
Traefik unterstützt viele weitere Anbieter für die DNS-Challenge. Eine Liste gibt es in der Dokumentation: https://doc.traefik.io/traefik/https/acme/#dnschallenge
Wird ein anderer Provider eingesetzt, müssen in der docker-compose.yml
von Traefik die Variablen, die mit "NETCUP_" beginnen, entfernt und stattdessen die Variablen für den jeweiligen Provider (siehe Traefik Doku) eingesetzt werden.
In this document, I will explain how to setup nut
(Network UPS Tools) on Ubuntu 18.04 and 20.04.
It is basically the next chapter of my previous gist, Upgrade nut on Ubuntu 18.04.
I'll only document USB
connected UPS and not the other supported connection modes.
Gist to support https://www.youtube.com/watch?v=vMlUVDcriww
- https://github.com/GoogleContainerTools/kaniko
- https://docs.cloudbees.com/docs/cloudbees-ci/latest/cloud-admin-guide/using-kaniko
kubectl create secret docker-registry docker-credentials --docker-username=[userid] --docker-password=[Docker Hub access token] --docker-email=[user email address] --namespace jenkins
Accessing a subnet that is behind a WireGuard client using a site-to-site setup
We want to access a local subnet remotely, but it is behind a NAT firewall and we can't setup port forwarding. Outgoing connections work, but all incoming connections get DROPPED by the ISP's routing policy.
This guide creates a reverse SSH tunnel to route all Plex server traffic through it.
Step 2 is done on the tunnel, all other steps are done on the plex server.
On plex server:
#!/bin/bash | |
# Copyright © 2021 Chirag Bhatia | |
# Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: | |
# The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. | |
# THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOF |