https://www.windmill.dev/docs/advanced/self_host#update
Here are simple one-liners for backing up and restoring your Windmill PostgreSQL database:
https://www.windmill.dev/docs/advanced/self_host#update
Here are simple one-liners for backing up and restoring your Windmill PostgreSQL database:
| blueprint: | |
| name: Party Lights (Label Support) | |
| author: AntonH (Modified for labels) | |
| homeassistant: | |
| min_version: "2024.10.0" | |
| description: | | |
| **Version 3.2L (Label Support)** | |
| Lights go to party mode (color loops or fade-in-and-out) | |
| ⚠️ **NOTE:** ⚠️ | |
| *This automation is triggered by the status of a switch or an input_boolean entity.* |
Shoutout @del13r for posting a great tutorial on the community forum and indepth feedback on GitHub issues.
Ecowitt can only send stats to HTTP API endpoints and we want to keep our Home Assistant secure via HTTP/s access only.
| #cloud-config | |
| autoinstall: | |
| version: 1 | |
| ssh: | |
| install-server: true | |
| # option "allow-pw" defaults to `true` if authorized_keys is empty, `false` otherwise. | |
| allow-pw: false | |
| # "[late-commands] are run in the installer environment with the installed system mounted at /target." |
This is specifically for testing unreleased k8s components. Most of this is from https://cloud.google.com/artifact-registry/docs/docker/quickstart
Fixes errors in Kubernetes v1.22+:
kubelet cgroup driver: \"cgroupfs\" is different from docker cgroup driver: \"systemd\""kubelet cgroup driver: \"systemd\" is different from docker cgroup driver: \"cgroupfs\""By setting both to use systemd as preferred by kubeadm.
Kubeadm: remove the automatic detection and matching of cgroup drivers for Docker. For new clusters if you have not configured the cgroup driver explicitly you might get a failure in the kubelet on driver mismatch (kubeadm clusters should be using the systemd driver). Also remove the IsDockerSystemdCheck preflight check (warning) that checks if the Docker cgroup driver is set to systemd. Ideally such detection / coordination should be on the side of CRI implementers and the kubelet. Please see the page on [how to configure cgroup drivers](https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/