Jeroen De Meerleer
- Updated doctrine/orm from version ^2.15 to ^2.16 - Updated guzzlehttp/guzzle from version ^7.7 to ^7.8 - Updated nelmio/security-bundle from version ^3.0 to ^v3.0 - Updated symfony/flex from version ^2.3 to ^v2.4 - Updated symfony/webpack-encore-bundle from version "^v2.0" to "^v2.1" - Updated laminas/laminas-code from version 4.12.0 to 4.13.0 - Updated doctrine/annotations from version "^2.0" to "^2.0.1" - Updated laminas/laminas-coding-standard from version "^2.
(c) 2017-2018, 2021- Jeroen De Meerleer email@example.com
Webcron management is an easy-to-use interface to manage cronjobs running on a publicly available http-location.
Requirements for build-server
- php <= 8.1 (incl composer <= 2, ext-pcntl, ext-openssl, ext-intl)
- NodeJS <= 16.0 (incl. npm <= 8)
Please run following command on the build server
$ composer install --no-dev --optimize-autoloader $ npm install $ npm run build $ rm -rf node_modules # Node modules are only required for building
- php <= 8.1
- ext-pcntl (highly recommended)
- SSH-access to the server
- Ability to change the webroot directory
- Ability to run a script as daemon (eg. supervisor or systemd units)
Create a build yourself or download the build from the releases page
Upload the build to the webserver.
Set up your webhosting to use the
/publicdirectory as web root
Create the .env file by copying .env.sample to .env and change the values
php bin/console doctrine:migrations:migrateto create or migrate the database
Create a first user by running
php bin/console webcron:user add
Set up the daemon script using systemd, supervisord or similar system
If this is not possible running the daemon using a cronjob is still possible using below gist (Not recommended)
0 * * * * cd /path/to/webcron/ && php webcron daemon --time-limit=3600 > /dev/null 1&>2
Same requirements and deploying
- Remove all files except .env from the webserver
- Upload the new build to the webserver
php bin/console doctrine:migrations:migrateto migrate the database
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.