![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
That depends on if you trust them. Also, would this be your only backup?
That depends on if you trust them. Also, would this be your only backup?
There are some things that are easier to see and check in Portainer, but for pure compose handling (up, down, logs) dockge works really well.
I run a mixed setup, many of the “less important” containers are on watchtower auto-update, the rest on notification (reverse proxy, Nextcloud, etc).
But I also have many of them on specific branches instead of “latest”.
Any special requirement for Alpine, or just “because I want to”?
I’d be a bit concerned with having the git repo also be hosted on the machine itself.
Please tell me you have a tested backup solution/procedure in place.
Do you have a server, connection and domain available?
If yes, a simple Joomla setup with a single static page should work well.
and it was tasty but so sweet it could have been served for dessert.
To be fair, the whole point of a Tarte Tatin is to caramelize whatever you put on there. I’d imagine it’ll be quite hard to find a good combination that’s not sweet and still caramelizes properly.
Moved from ZHA to Z2M. Much easier to handle as I already ran an MQTT container, and re-connecting devices to Z2M doesn’t mess with the HA devices.
Nice haul! I hope you also managed to get the small power plant for the drives. That’s not going to be pretty.
That’s most likely the syslog. Check the settings, you can choose the volume to use for it.
Which is one of the occasions that a Dev sticks to the original feature list instead of trying to shoehorn in some features which wouldn’t really fit.
While I do love Syncthing, it solves a different set of requirements.
Grafana + Prometheus + data gathering will at least give you the resource and usage stats.
Subtitles being “burned into” the frames instead of being a separate track, also known as hard-coded sometimes. This enables one to use subtitles on devices which cannot traditionally use them or screw up the display. But this means the server needs to re-encode each and every frame, which is a massive load on the server.
tasty
Being tasty is mostly a matter of spices. Apart from your dead microwave, what do you have in your kitchen?
Considering it’s basically just a script “frontend”: wireguard and its documentation.
That setting also takes host names. As long as both containers share at least one network, put in the service name (not the container_name!), e.g. “npm” or whatever yours is called and you should be fine.
What are you using as a database? Also, from which Gitea version to which Forgejo version did you attempt the migration?
Have you considered other protocols, especially ZigBee?