Editing the plain text crontab is error prone for managing jobs, e.g., adding jobs, deleting jobs, or pausing jobs.
A small mistake can easily bring down all the jobs and might cost you a lot of time. With Crontab UI, it is very easy to manage crontab.
Here are the key features of Crontab UI.
Easy setup. You can even import from existing crontab.
Safe adding, deleting or pausing jobs. Easy to maintain hundreds of jobs.
Backup your crontabs.
Export crontab and deploy on other machines without much hassle.
Error log support.
Mailing and hooks support.
TIP ME !
Your gratitude and finance will help me to continue integration of this QPKG and maintain up to date versions.
Your gratitude and finance will help me to continue integration of this QPKG and maintain up to date versions.
Last update: 25 October 2024
Carson –
Not working at all. It requires username and password to login, but there is nowhere we can set or get username/password.
dft601 –
It is working…
user: qnap
password is your hostname…
You can find it in file CrontabUI.sh
Artur –
The concept is great, but sadly the TS-NASARM_64 package is incompatible with Annapurna Labs Alpine AL-514 quad-core 1.7 GHz ARM® Cortex-A15 Processor on the QNAP TS-1635 model, so could not even install….
Gregory Schlein –
HOST=0.0.0.0 PORT=12345 BASIC_AUTH_USER=qnap BASIC_AUTH_PWD=$HOSTNAME ./crontab-ui &
echo $! > $PIDF
What is my hostname .
I apparently need this to log in !! WTF
Mike –
Your hostname is the name of you NAS. The server name.
You find it on the NAS… Overview or in the control panel…
Evgenii Timofeev –
Good app! Thank You! Work on TES-1885U
Cameron M Kracke –
Is it possible to use a different use ID, such as my Qnap Admin account? If so, I assume this change can be made by modding the CrontabUI.sh/. Can you please confirm?
richbrew –
this app seems to interact directly with crontab. however, based on this article from qnap, this method wont work for qnap.
https://wiki.qnap.com/wiki/Add_items_to_crontab
anything added through crontab gets removed daily unless it is manually added to /etc/config/crontab
QoolBox –
it is using his own cron engine
Arnaud1110 –
Great concept: qnap should take that into account for evolutions. But for me it doesn’t work. I’m referring to https://github.com/alseambusher/crontab-ui/issues/253. It seems Stephane (Qoolbox aka QNAP_Stephane) could do something for improving the packaging into qnap.
I just copy here my initial issue :
I tried to install and use crontab-ui (CrontabUI_0.3.16_arm_64.qpkg) on my nas qnap (qts 5.1.8). For installing in the qts App Center, I use an administrator account MyName (not the admin account which is desactivated). On the surface in the interface it looks good : I can create et run some tests jobs.
BUT
– using this crontabui tool allows the creation of scheduled tasks, but by … overwriting the contents of the system crontab (all standard tasks have disappeared)! So, after creating 2 jobs, the crontab of the user MyName contains only these 2 jobs (and all the standard jobs have disappeared).
– and when the system is restarted, the system crontab is back in place (so the crontab of the user MyName contains the standard jobs), but the tasks generated by the crontabui tool have disappeared…
What did I do wrong in this case? And How could I resolve this issue?
Thank you for any idea…
Arnaud
Andrea –
Not working for me (TS-464eu) with QTS 5.2.0. It looks like crontab UI modifies only “crontab -e” file, and this is not correct from QNAP perspective. So the script added inside from it don’t work. 3 stars because the idea is great, hope it will be corrected in future releases