Jeroen De Meerleer
||1 week ago|
|cache||4 years ago|
|config||1 month ago|
|lib/Framework||1 month ago|
|public||1 week ago|
|src||1 week ago|
|storage||1 week ago|
|templates||1 week ago|
|webcron.old||1 week ago|
|.env.sample||1 month ago|
|.gitignore||1 month ago|
|LICENSE.md||1 month ago|
|README.md||1 month ago|
|bootstrap.php||1 month ago|
|composer.json||1 month ago|
|composer.lock||1 week ago|
(c) 2017, 2021 Jeroen De Meerleer firstname.lastname@example.org
Webcron management is an easy-to-use interface to manage cronjob running on a publicly available http-location.
I'm currently in the process of rewriting the application to more modern standards. The current main branch is very unstable at the moment. Please don't use it.
I encourage everyone to wait for the new version as upgrading will probably be very difficult.
What will change with the rewrite?
- All urls will change. eg. /login/ and /jobs/5/edit/ instead of /login.php and editjob.php?jobId=5
- Dropping support for directly calling webcron.php from url-bar
- Daemonized main-script which will enable running cronjobs by seconds
- Webserver able to run PHP
- PHP 8.0 or greater
- MySQL/MariaDB (Or sqLite)
- Ability to add a system cronjob for installation (You can maybe ask you webhost?)
Follow the instructions below to install the webcron interface
- Copy this repository to a public directory on your server
- Create a database using the database.sql provided in the repository
- Create a first user by inserting a first record to the users table (Password is hashed with bcrypt)
composer installto install dependencies.
- Open ssh and add following line to your crontab
* * * * cd /path/to/webcron/ && php webcron.php > /dev/null 1&>2
Cronjobs are not running
Did you edit the crontab?
I can't do an automatic system upgrade!
Doing a system upgrade requires sudo which has a certain number security measurements. To enable running anything with sudo (eg.
sudo apt dist-upgrade -y) the user needs to be able to run sudo without tty and password.
Can I schedule a reboot every week?
Yes, you can do this by creating a job with
reboot as "url". When this job needs to run, the reboot is triggered to run at the very end. At the first run of the master script a list of active and terribly failed services is pushed to the job so you can check this if something is wrong.