-
Notifications
You must be signed in to change notification settings - Fork 0
Installation
Currently only Apache is supported out of the box, as i'm lacking the time and experience to test on other servers. Any configuration help for nginx, etc... will be appreciated folks!
You need to make sure to have your webserver configured for PHP 5.3.0 as minimum (5.3.8+ recommended) and the rewrite module enabled (on a typical modern apache2 installation you can do this via sudo a2enmod rewrite
).
Download the cronman repository into a directory of your choice - that said, if you don't/can't use symlinks or plan to set up an own vhost (which is strongly recommended but not necessarily needed to operate CronMan) you must of course select a directory that is accessible to apache (your "wwwroot" root folder, which will be under "/var/www" on a default *nix installation).
- (Strongly recommended but optional) Setup an own vhost, pointing to www/public/
- Navigate to the Vhost / Subdomain entry used in 1. or (if you skipped that step) call it up using your server address plus /{CRONMAN_SOURCE_DIRECTORY}/www/public
- You most likely will see an error page (if you don't, don't worry and continue to step 4.) - this is standard yii installation stuff which basically comes down to the following
chmod 767 www/assets; chmod 766 www/runtime; chmod 766 www/data
- CronMan will know it is freshly installed and offer you to go to the setup screen. Do that and the guided setup procedure will begin.
You will get to the prerequisites screen, where the your server environment is going to be analysed:
On the next screen you select your database type (currently only Postgresql supported):
Enter your database connection details:
In case something goes wrong, you will be shown the underlying error message which may help you review the connection details for possible mistakes:
OK, connection fixed:
Next, Cronman will check if there is already a database of the same version installed:
If not, you may create the database at the click of a button - given the supplied database login has sufficient permissions: