Coral CC Release Information
|Build Date||10 December 2019|
|Build Date||10 December 2019|
All support requests for CodeCanyon products must be initiated using Envato's messenger or by posting a comment on the CodeCanyon product page.
Start by opening the installation.txt file in the main CodeCanyon zip file. Follow the instructions in this file, in order, to get up and running fast. Make sure you edit your config.php file using your favorite text editor before uploading Coral to your website. Finally, ensure you navigate to your install directory on your website and do your initial database setup, which includes installing the database tables and setting up your account. After you have successfully logged in using the account you created, delete the app/routes/install.php file to prevent someone from coming in behind you and creating their own account.
Coral is designed to show the full paths to files that it monitors. Due to this, I cannot demo this on my own site for security reasons. I know it seems like an inconvenience, but the video demo, product page on my website, and the CodeCanyon product page collectively show Coral in action and offer numerous screenshots and describe the features. Trust me, it is worth more than $27 USD and you won’t be disappointed! If you have pre-sales questions, i.e. want to see pictures or Coral in action, just email me.
Using your host's cPanel, you will need to select Cron jobs and create a new Cron job. Depending on what is installed on your server, you could run one of the following commands at specified intervals (which you select from your cPanel interface):
Note: Replace "scan_type" with your desired scan. The options are: live, quick, comp, and ss. Monitor slug is the hyphenated simple name for your monitor, and the id represents the database record id of your monitor. These paths are generated automatically for you, so all you need to do is got to your monitor's options page and scroll to the bottom. Copy the provided code into your Cron GUI and off you go!
cd /home/username/public_html/coral; php coral.php scan:scan_type 'monitor-slug'
php -q /home/username/public_html/coral/cron/mysecreykey/scan/scan_type/id
lynx -dump http://www.yoursite.com/coral/cron/mysecreykey/scan/scan_type/id &> /dev/null/
curl --silent http://www.yoursite.com/coral/cron/mysecreykey/scan/scan_type/id &> /dev/null/
Note: Some hosts have limits on how often Cron jobs can be ran. I recommend to run a comprehensive scan on your monitor at least once per hour.
If you setup a monitor for a folder that has in excess of 40K files, you will probably run into some memory errors. There are a couple ways to deal with this, but it depends on what your web host allows. If you have access to your php.ini file and can make changes, you will need to bump up your memory_limit value. 32M is good for sites that have less than 10K files. Anything greater than that and you will need to adjust this up to 64M or higher, depending on your specific situation.
Another work around, is that you should break large folders up into smaller monitors. Coral will give you a warning message on the monitor's index page if your monitor is too large. If you can't break up the site, due to the way your site, or client's site is structured, then you will have to bump up your PHP memory limit.
Another thing to consider is that Apache might be configured to timeout scripts after a certain period (usually 30 seconds). If you know how to edit your Apache httpd.conf file, then you can do that as well. However, doing that is way beyond the scope of this support question!