Moving install info to INSTALL.md file and updating it;
adding file permission changes to makefile
This commit is contained in:
Pepijn Over
parent
9e788e0971
commit
6d5397bf61
|
|
@ -0,0 +1,72 @@
|
|||
# PHP Server Monitor
|
||||
|
||||
## Install
|
||||
|
||||
### 1. Upload files
|
||||
|
||||
The first step is to upload your files to your webserver where you can reach them.
|
||||
You can rename the folder of the server monitor without any problems.
|
||||
|
||||
### 2. Run install.php
|
||||
|
||||
You can now run the install.php script located in the root dir.
|
||||
|
||||
The install script will guide you through setting up your configuration file and create the required database tables.
|
||||
If for some reason you can not generate your configuration file, you can do it manually using the steps below.
|
||||
Rename the config.php.sample file to config.php, then open the config.php file with a plain text editor such as Notepad.
|
||||
In this file you need to change the database information, which is stored using php's define() function.
|
||||
To change these values correctly, only update the second parameter of the function.
|
||||
|
||||
define('PSM_DB_HOST', 'db_host');
|
||||
define('PSM_DB_NAME', 'db_name');
|
||||
define('PSM_DB_USER', 'db_user');
|
||||
define('PSM_DB_PASS', 'db_user_password');
|
||||
|
||||
For example: to change your username you should ONLY change the 'db\_user' part.
|
||||
Do NOT remove the quotes around your username as that will result in an error.
|
||||
After you have created the config.php, run the install.php again to create the database structure.
|
||||
|
||||
### 3. Configure your installation
|
||||
|
||||
Open the main page of the server monitor, by simply navigating to index.php. In the menu on the top find "Config",
|
||||
it will open a page where you can change the necessary information for your tool.
|
||||
|
||||
|
||||
## Upgrade
|
||||
|
||||
For a regular upgrade, follow these steps:
|
||||
|
||||
* Replace all files except(!) config.php
|
||||
* Navigate to install.php
|
||||
* Follow the steps
|
||||
* Enjoy
|
||||
|
||||
### From 2.0
|
||||
|
||||
The structure of the project has changed quite a bit since 2.0, but if you have not made any local changes the upgrade is quite easy.
|
||||
The best thing to do is to replace all your current files with the new release, except for the config.inc.php file.
|
||||
The config file has actually been renamed since 2.0, but if you keep it there while upgrading the install script will use it to prefill your database information.
|
||||
The rest of the steps are identical to a regular upgrade (see above), except that you can remove the old config.inc.php file afterwards.
|
||||
|
||||
### From 2.1
|
||||
|
||||
One of the new features introduced in 2.2 is a user authentication system. Because the users in previous versions do not have a password, after upgrading you would not be able to login.
|
||||
For that reason the upgrade script will ask you to create a new account during the upgrade, which you can then use to change the password for the existing accounts.
|
||||
If, for whatever reason this does not work, the upgrade script automatically change the username of all existing users to their email addresses, which you could use for the forgot password screen.
|
||||
|
||||
## Setting up a cronjob
|
||||
|
||||
In order to keep the server monitor up to date, the status updater has to run regularly.
|
||||
If you're running this on a linux machine, the easiest way is to add a cronjob.
|
||||
If it is your own server or you have shell access and permission to open the crontab, locate the "crontab" file
|
||||
(usually in /etc/crontab, but depends on distro). Open the file (vi /etc/crontab), and add the following
|
||||
(change the paths to match your installation directories) to run it every 15 minutes:
|
||||
|
||||
*/15 * * * * root /usr/bin/php /var/www/html/phpservermon/cron/status.cron.php
|
||||
|
||||
As you can see, this line will run the status.cron.php script every 15 minutes. Change the line to suit your needs.
|
||||
If you do not have shell access, ask your web hosting provider to set it up for you.
|
||||
|
||||
The update script has been designed to prevent itself from running multiple times. It has a maximum timeout of 10 minutes.
|
||||
After that the script is assumed dead and the cronjob will run again.
|
||||
If you want to change the 10 minutes timeout, find the constant "PSM_CRON_TIMEOUT" in src/includes/psmconfig.inc.php.
|
||||
2
Makefile
2
Makefile
|
|
@ -12,6 +12,8 @@ export:
|
|||
mkdir ./build ./build/phpservermon
|
||||
git archive $(tag) | tar -xf - -C ./build/phpservermon/
|
||||
find ./build/phpservermon -name "*.php" -exec sed -i "" "s/@package_version@/$(tag)/" {} \;
|
||||
find ./build/phpservermon -type f | xargs chmod 0644
|
||||
find ./build/phpservermon -type d | xargs chmod 0755
|
||||
cd ./build; zip -rq phpservermon-$(tag).zip ./phpservermon; cd ../;
|
||||
cd ./build; tar -pczf phpservermon-$(tag).tar.gz ./phpservermon; cd ../;
|
||||
rm -rf ./build/phpservermon
|
||||
|
|
|
|||
72
README.md
72
README.md
|
|
@ -54,73 +54,7 @@ The latest version can be downloaded from <http://www.phpservermonitor.org/>.
|
|||
|
||||
## Install
|
||||
|
||||
### 1. Configuration
|
||||
|
||||
The install script will guide you through setting up the configuration, but if you want to be ahead of the game, you can do this one first.
|
||||
Rename the config.php.sample file to config.php, then open the config.php file with a plain text editor such as Notepad.
|
||||
The first thing to do is to get your database login information right.
|
||||
The information is stored using php's define() function.
|
||||
To change these values correctly, only update the second parameter of the function.
|
||||
For example:
|
||||
|
||||
define('PSM_DB_USER', 'db_user');
|
||||
|
||||
To change your username you should ONLY change the 'db\_user' part.
|
||||
Do NOT remove the quotes around your username as that will result in an error.
|
||||
If you do not feel comfortable doing this, skip this step and the install script will generate it for you.
|
||||
|
||||
### 2. Upload files
|
||||
|
||||
The next step is to get your files onto your webserver where you can reach them.
|
||||
You can rename the folder of the server monitor without trouble.
|
||||
|
||||
### 3. Run install.php
|
||||
|
||||
You can now run the install.php script located in the root dir.
|
||||
|
||||
### 4. Configure your installation
|
||||
|
||||
Open the main page of the server monitor, by simply calling index.php. In the menu on the top find "config",
|
||||
it will open a page where you can change the necessary information for your tool.
|
||||
|
||||
|
||||
## Upgrade
|
||||
|
||||
For a regular upgrade, follow these steps:
|
||||
|
||||
* Replace all files except(!) config.php
|
||||
* Navigate to install.php
|
||||
* Follow the steps
|
||||
* Enjoy
|
||||
|
||||
### From 2.0
|
||||
|
||||
The structure of the project has changed quite a bit since 2.0, but if you have not made any local changes the upgrade is quite easy.
|
||||
The best thing to do is to replace all your current files with the new release, except for the config.inc.php file.
|
||||
The config file has actually been renamed since 2.0, but if you keep it there while upgrading the install script will use it to prefill your database information.
|
||||
The rest of the steps are identical to a regular upgrade (see above), except that you can remove the old config.inc.php file afterwards.
|
||||
|
||||
### From 2.1
|
||||
|
||||
One of the new features introduced in 2.2 is a user authentication system. Because the users in previous versions do not have a password, after upgrading you would not be able to login.
|
||||
For that reason the upgrade script will ask you to create a new account during the upgrade, which you can then use to change the password for the existing accounts.
|
||||
If, for whatever reason this does not work, the upgrade script automatically change the username of all existing users to their email addresses, which you could use for the forgot password screen.
|
||||
|
||||
## Setting up a cronjob
|
||||
|
||||
In order to keep the server monitor up to date, the monitor.php file has to run regularly.
|
||||
If you're running this on a linux machine, the easiest way is to add a cronjob.
|
||||
If it is your own server or you have shell access and permission to open the crontab, locate the "crontab" file
|
||||
(usually in /etc/crontab, but depends on distro). Open the file (vi /etc/crontab), and add the following
|
||||
(change the paths to match your installation directories) to run it every 15 minutes:
|
||||
|
||||
*/15 * * * * root /usr/bin/php /var/www/html/phpservermon/cron/status.cron.php
|
||||
|
||||
As you can see, this line will run the status.cron.php script every 15 minutes. Change the line to suit your needs.
|
||||
If you do not have shell access, ask your web hosting provider to set it up for you.
|
||||
|
||||
The update script has been designed to prevent itself from running multiple times. It has a maximum timeout of 10 minutes.
|
||||
After that the script is assumed dead and the cronjob will run again.
|
||||
See INSTALL.md file.
|
||||
|
||||
|
||||
## Contributing
|
||||
|
|
@ -151,10 +85,6 @@ The second part is the actual message. There are a few variables you can use in
|
|||
* %ERROR% This one only works for the off_* messages and contains the error returned by the monitor
|
||||
|
||||
|
||||
## Credits
|
||||
|
||||
See CREDITS file.
|
||||
|
||||
## License
|
||||
|
||||
PHP Server Monitor is free software: you can redistribute it and/or modify
|
||||
|
|
|
|||
Loading…
Reference in New Issue