A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (donβt cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Well the services would have to speak the same event or messaging system, whatever it may be. Then you'd just need to bridge the networks of the containers, or have them speak to endpoints in each side.
There is no universal messaging system between all pieces of software though. Maybe figure out what you're sending to first, then work back from there. There's nothing blocking you from sending data between two containers in a variety of ways though.
would running nut-monitor in the VMs fit your use case?
But it would a cleanest of running at only one place and fetch the infos after
my solution to this is to only deal with the UPS in proxmox. it shuts down everything if the battery goes below a certain level.
I think you can configure nut to run a few scripts when something changes around the UPS. you could have a script that sends an alert through ntfy, and/or the web services that you want to use for this, but I'm not familiar with the notification system of nextcloud and truenas
Okay going to check it
one more thing I remembered when re-reading the title: I think you can send messages to the VM using the qm command. it stands for qemu monitor, basically its a management tool