From my understanding and experience each device you're logged into gets the hardware survey a few times a year.
misterbngo
joined 1 year ago
The way I've been using it for a few years is that most of my machines can see each other and I have a shared folder and versioning setup. As I add things they move between the different machines and once an additional machine has it it is available to the others until everything is in sync
You can definitely do chain topologies which are useful for certain things with a single source of truth
As a note, I believe that syncthing will actually scale up with more nodes as they will all share with each other if they know each other. If you're doing this 1 to many then this is not the case of course.
Ive actually been personally moving away from kubernetes for this kind of deployment and I am a big fan of using ansible to deploy containers using podman systemd units, you have a series of systemd .container files like the one below
[Unit]
Description=Loki
[Container]
Image=docker.io/grafana/loki:3.4.1
# Use volume and network defined below
Volume=/mnt/loki-config:/mnt/config
Volume=loki-tmp:/tmp/loki
PublishPort=3100:3100
AutoUpdate=registry
[Service]
Restart=always
TimeoutStartSec=900
[Install]
# Start by default on boot
WantedBy=multi-user.target default.target
You use ansible to write these into your /etc/containers/systemd/ folder. Example the file above gets written as /etc/containers/systemd/loki.container.
Your ansible script will then call systemctl daemon-reload and then you can systemctl start loki to finish the example
I assume ppl still run bzflag servers