OliveTin VS webhook

Using OliveTin would be a fantastic solution. (Just make a button that starts the server and call it a day)

Have a look at https://github.com/OliveTin/OliveTin

If the users will only need to run the scripts and not worry about what it's doing, I would suggest Olive Tin. It's meant for shell scripts, but you could just as easily have a shell script call powershell.

Olivetin is made for this use case in mind. You just need a way to protect the interface via an auth mechanism, and create a simple script to use the proxmox API to restart the VM!

For these kinds of things I'm a fan of using something like OliveTin. Restarting Plex is funnily enough an example they use on their site.

I recently found OliveTin for use cases like this.

Try this awesome tool https://github.com/adnanh/webhook and you can make any bot you wish

Something like this: https://github.com/adnanh/webhook for a low code solution. This is the just the top hit, there tons of “Linux WebHook receivers” out there. Container A has the WebHook config to run ffmpeg. Container B runs curl to trigger the WebHook. Can be instrumented with fairly simple shell script.

If all you need is a Webhook trigger, you might want to take a look at https://github.com/adnanh/webhook

I thought this is for receiving webhooks at first glance, like another alternative for node-red, n8n.io, and adnanh/webhook.

you can register a webhook on github and listen to it from your second pc using https://github.com/adnanh/webhook

I occasionally trigger playbooks using this simple go project https://github.com/adnanh/webhook.

You can do a hell of a lot with webhooks, a bit of scripting and, err, webhook.

I use https://github.com/adnanh/webhook to deploy the changes in the git repository to the server and have it run docker compose up -d. I actually just modified it this week to run the docker commands in a background queue using https://vicerveza.homeunix.net/~viric/soft/ts/ (commands are added to a queue and run in the order they were added, useful for long-running commands) this way webhook can reply that the git repository was updated on the server and the docker compose command was added to the task queue and webhook doesn't timeout.