OliveTin VS Cronicle

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.

Wasn't it simpler to use Cronicle (https://github.com/jhuckaby/Cronicle)?

You can give cronicle a try. It has a web based UI and sone good stats.

Have a look at Cronicle ( https://github.com/jhuckaby/Cronicle )

Firstly, I tried Rundeck and Apache Airflow. They are complete overkill for what I want to do. Then I found Cronicle which is light enough, besides it can pull double duty as a general purpose scheduler.

Also check out http://cronicle.net/

Would recommend https://github.com/jhuckaby/Cronicle for anyone running cronjobs but would like to have an interface. It has plenty of features, logs, resource stats, and notifications. Plus it's easy to setup.

Thought I'd post here before taking a dive into this and see if anyone has any practical experience. I'm looking for centralising scheduled tasks for multiple servers, preferably with a management GUI for friendliness. I found Crontab-UI which seems to only interact with the single host's crontab. Then I stumbled upon Cronicle which looks feature rich but looks like multi-server is handled by deploying the GUI to each host. A central server + agents on each host would be nicer. I'm wondering if anyone uses Cronicle, or another solution? Thanks!