
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.


Hi, I went through your logs and it seems like
crontabis not installed on the host machine?stderr: 'sh: 1: crontab: not found'The tool uses the host
crontabcommand viansenterto manage cronjobs, so it only works if ran from hosts that leverage crontab to run cron jobs.If that’s not the issue let me know and we can try and debug it together further, but looking at the logs it really seems like crontab is just not installed on your nas (guessing it’s a nas looking at the volume1 path)
p.s.
Thank you for the screenshots acknowledgment, I absolutely hate not having a visual aid on repositories when I want to try a new tool, I like to see what I am getting into before I get into it, and I absolutely judge a book by its cover, I am a frontend tech lead, UI is extremely important to me, if an app doesn’t have a somewhat clean UI I kinda refuse to even try using it hahah
Hmmmm…
systemctl status cron● cron.service - Regular background program processing daemon Loaded: loaded (/lib/systemd/system/cron.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2025-11-12 17:09:55 UTC; 1 day 2h ago Docs: man:cron(8) Main PID: 996 (cron) Tasks: 1 (limit: 47901) Memory: 358.5M CPU: 59.110s CGroup: /system.slice/cron.service └─996 /usr/sbin/cron -f -PI’ll dick around with it some more. I don’t want to hammer you right in the middle of your promo.
Meh, I want to make sure things work, that’s also part of the promo right? haha
run
which crontabfor me? I can see cron is running but I still am not sure you have crontab installed on the host machine if that makes senseShould’ve included that. My bad.
~# which crontab /usr/bin/crontabI’m always down to learn from those more knowledgeable than I.
Oh wow, that definitely threw me off lol anyhow, I don’t think I am more knowledgeable than you at all, I just know the tool I built more, so I can help figure out the nuances of it…
I have a feeling nsenter is not liking your nas for some reason, I wanna try a workaround and if it works for you I’ll go through the code and sort it out so we can use a proper env variable for this
add this env variable for now and tell me if it sorts you out <3
environment: - PATH=/usr/bin:/bin:/usr/local/bin:/usr/sbin:/sbin:$PATH