Selfhosted

Hi,
A small chunk of you of you may know me for my app Jotty, however I also published a slightly less popular (entirely open source) app called Cr*nmaster.

repo: https://github.com/fccview/cronmaster

Cr*nmaster (cronmaster) is a pretty powerful tool that allows you to view/create/edit/manage all your host cronjobs comfortable from an intuitive UI, it has features such as pausing jobs, adding comment to them, running them right from the UI, and from the latest update you'll be able to have nicely structured logs for your jobs on top of exit statuses being shown right there and then. You will be able to see if a job failed at a glance and view the logs to see what's going on.

I have also added translations that can be customised locally on your own machine (or you can be an angel and create a pull request with your own language so we can officially support it, together!)

The whole thing is very easy and straightforward to setup both with and without docker, the repository has a lot of guides in the `howto` folder on top of a very verbose readme file.

Here's a few of the key features:

• View/edit/delete/run your cron jobs from an intuitive UI
• Log your cronjobs (it uses a proprietary wrapper, you can modify the wrapper as much as you like from the mounted ./data folder).
• At glance exit statuses for all your jobs
• System stats to see how healthy your host machine is
• Ability to create custom scripts (using handy snippets - which you can easily add more of) for your cron jobs straight from the UI, these scripts are stored in your mounted folder and can be easily used when creating a cron job

All this to say that I am extremely excited for everything that's coming with this latest update, you can read about the latest release and all the improvements that came with it here

Let me know your thoughts and if you run in any issues i'm fairly active on github and on my discord server :)

NOTE for docker users:
Due to this needing to be able to read crontabs the docker has to run as root and have read/write access to your cron jobs. There was no way around it, so I suggest you keep this within your home network and not exposed to the web for security reasons.