@ -8,3 +8,7 @@ __crontab-ui is running but is not accessible on browser__ -
This is usually because the place where your crontab-ui is installed does not give access to others. It can be resolved by either giving permission to the user (Recommended) or running crontab-ui as root. Refer [this](https://github.com/alseambusher/crontab-ui/issues/8)
This is usually because the place where your crontab-ui is installed does not give access to others. It can be resolved by either giving permission to the user (Recommended) or running crontab-ui as root. Refer [this](https://github.com/alseambusher/crontab-ui/issues/8)
__Hosting crontab-ui : it works on localhost but not outside the server__ - You have to host it using nginx, apache2, etc. Refer [this](nginx.md).
__Hosting crontab-ui : it works on localhost but not outside the server__ - You have to host it using nginx, apache2, etc. Refer [this](nginx.md).
__crontab-ui stopped working__ - It can happen that your crontab-ui can stop working for some reason like adding incorrect jobs or timings. In order to fix it, you can just go ahead a remove the job from `crontab.db` or `env.db` in "crontabs" folder and restart crontab-ui.
__Where is my root node_modules folder__ - You can find it by `npm root -g`
//{ command; } 2>/tmp/<id>.log|| {if test -f /tmp/<id>; then date >> <log file>; cat /tmp/<id>.log >> <log file>; rm /tmp<id>.log }
// hook is in beta
crontab_string+=tab.schedule+" { "+tab.command+" } 2> "+tmp_log+"; if test -f "+tmp_log+"; then date >> "+log_file+"; cat "+tmp_log+" >> "+log_file+"; rm "+tmp_log+"; fi \n";
if(tab.hook){
lettmp_hook="/tmp/"+tab._id+".hook";
crontab_string+=tab.schedule+" ({ "+tab.command+" } | tee "+tmp_hook+") 3>&1 1>&2 2>&3 | tee "+tmp_log+
letmessage="<p>This is based on nodemailer. Refer <a href='https://github.com/alseambusher/crontab-ui/tree/master/README/mail.md'>this</a> for more details.</p>";