File Release Notes and Changelog
Release Name: Monolith 0.8beta
Notes: ############################################################### MySQL Monolith Backup Manager Written by Matt Reid http://themattreid.com irc.freenode.net #cisco,#mysql,#solaris,#fedora /nick Lumberg themattreid@gmail.com Licensed under the GPL: http://www.gnu.org/licenses/gpl.txt ################################################################ VERSION: 0.8beta ################################################################ Contents: 1. Install 2. Use 3. Troubleshoot 4. Changelog 1. Install - Untar/gzip the package in your web root. `tar xvzf monolith.tar.gz` for example, or `gzip -d monolith.tar.gz && tar xvf monolith.tar` - Set the database connection information in two files: inc/dbconn.php and cron/cronexec.sh inc/dbconn.php $db = 'monolith'; $dbhost = 'monolith_host'; $dbuser = 'monolith'; $dbpass = 'monolith_user_pass'; ----- cron/cronexec.sh MONO_HOST="monolith_host" #mysql server that monolith is hosted on MONO_PASS="monolith_user_pass" #monolith db password MONO_USER="monolith" #monolith db user MONO_DB="monolith" #monolith db - Execute the sql file to create the monolith database, this is run from the install directory. mysql -uroot -p --host=hostname_of_your_mysql_server < sql/monolith-FINAL.sql 2. Use - Point your browser to the install directory. If you untarred it in /var/www/html then it should be /var/www/html/monolith and the web page is at http://yourhost/monolith/index.php - Login as admin/password or just admin with no password. One of the two. - Click "Manage System". The defaults *should* be fine if you're on Redhat/Fedora but tune to your needs. It needs to run as root at the current time so suck it up. Change your email reporting address - I don't want your database backup information sent to my address (the default). - Disable pruning if you like. See the note at the bottom of the page for info. - Click "Manage Databases" and then "Add Database" - fill in the appropriate fields. 3. Troubleshoot - Check the /var/log/monolith.log - it outputs lots of useful info - Check the $INSTALL_DIR/repo for your actual files. If the files are there and the monolith database isn't getting updated then something is up with the tmp sql file generation. - Last resort... email me or get me on IRC. 4. Changelog - added the hourly crond restart to /etc/crontab because /etc/cron.d/monolith wasn't being read into memory when applying updates. - updated the way temporary sql files are generated and location stored. - some other stuff that I did along the way but can't remember, but it's good ;)
Changes: 4. Changelog - added the hourly crond restart to /etc/crontab because /etc/cron.d/monolith wasn't being read into memory when applying updates. - updated the way temporary sql files are generated and location stored. - some other stuff that I did along the way but can't remember, but it's good ;)
