Struggeling with relocating

docs/en/CHANGELOG.txt

@@ -0,0 +1,52 @@
+$Id$
+
+Changelog of the most important changes compared to version 1.22 (1.23 never left the beta status):
+
+- MySQLDumper 1.24 is still working on PHP4 and PHP5
+- new, light and friendly style. The "old" style is still included. 
+- better use of RAM
+- backup and restore via PHP is about 25 percent faster
+- possibility to select tables when doing backup or restore
+- use different configuration profiles to manage different MySQL-Server or -user. 
+  This way you can administrate different MySQL-Server with a single MySQLDumper-Installation.
+- the internal SQL-Parser has been improved (more backups from other programms can be imported)
+- SQLBrowser: a lot of bugfixes and some improvements (nevertheless it must still be regarded as experimental)
+- SQLBrowser: a comfortable fulltext-search lets you find text even when you don't know in which column it can occur
+  After editing a record you get back to the hitlist. That is very comfortable if you need to change some data.
+- Tools: in version 1.22 the export of data as file didn't work. Now it is working again.
+- the Web-GUI has been simplified. Some parameters have been removed. (You nearly have no chance to configure something incorrectly :) )
+- FTP-Transfer: address up to 3 ftp configurations simultaneously in one backup process
+- Tables of type VIEW or MEMORY are now detected and data is not saved but the structure of the table is
+- the directory work/structure is no longer needed
+- the automatic "structure only" backup has been removed
+- better and safer handling of encodings of backup files
+- better and safer error-handling
+- the backup converter has been rewritten. Now it also automatically converts big files into Multipart files.
+- no notices in server-logs
+- when adding SQL-Queries to the SQL-Library you can now enter more than one query. If using "command before/after backup" 
+  these queries will be executed in a row. Success or failure is written into the log file. 
+- When creating a password protection the password strength is visualized.
+
+crodump.pl:
+- when you can call crondump.pl in the standard directory "msd_cron" you no longer need to enter the 
+  "$absolute_path_of_configdir" manually. An automatic detection was added. 
+- better and safer catching of errors
+- logging of events is much more precise and gives you clear information what happened
+- automatic deletion now regards Multipart files as one complete backup and works the way you expect it to work
+- automatic deletion is done after the backup process. In case of errors this retains your old backups you might need.
+- the config parameter - which configuration profile is to be used - can be set in 3 ways. The missing suffix
+  ".conf.php" will be added dynamically. 
+1. config=mysqldumper.conf.php
+2. config=mysqdumper.conf
+3. config=mysqldumper
+
+- removed signalhandler:
+When crondump.pl was started via a cronjob there was a malfunction. On some, rare server this signalhandler caused a second 
+or third instance of the script that never stopped and stuck in the process list. In this case the process must be killed manually.
+
+... and many more small or big bugfixes and cleaning up of the code
+
+When you want to know more, just take a look at the changelog of code changes at Sourceforge. Each change
+of the code is documented here:
+
+http://mysqldumper.svn.sourceforge.net/viewvc/mysqldumper/trunk/?view=log

docs/en/INSTALL.txt

@@ -0,0 +1,7 @@
+$Id$
+
+Installation:
+
+- upload the folder mysqldumper to any folder on your webspace
+- start the script in your browser (http://www.yourDomain.de/yourFolder/mysqldumper/)
+- Follow the Installation assistent

docs/en/README.txt

@@ -0,0 +1,80 @@
+$Id$
+
+MySQLDumper - Readme
+====================
+
+  MySQLDumper is a PHP and Perl based tool for backing up MySQL databases.
+  You can easily dump your data into a backup file and - if needed - restore it.
+  It is especially suited for shared hosting webspaces, where you don't have
+  shell access.
+
+  Version 1.25
+  ---------------
+  http://www.MySQLDumper.net/
+
+	Copyright (C) 2004-2010 Daniel Schlichtholz (admin@MySQLDumper.de) and more
+	
+	This program is free software; you can redistribute it and/or modify it under 
+	the terms of the GNU General Public License as published by the Free Software 
+	Foundation; either version 2 of the License, or (at your option) any later 
+	version.
+	
+	This program is distributed in the hope that it will be useful, but WITHOUT 
+	ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS 
+	FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more 
+	details.
+	
+	You should have received a copy of the GNU General Public License
+    along with this program; if not, write to the Free Software
+    Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
+	
+	
+  Requirements:
+    PHP 4 or later
+    MySQL 4.1 or later
+    a web-browser
+    optional Perl for cronscript
+
+  Summary:
+	The problem:
+	A PHP script has a maximum execution time that is usually set to 30 seconds on
+	most server installations. A script running longer than this limit will simply
+	stop working. This behavior makes backing up large databases impossible. Maybe
+	you already had this specific problem when using other tools.
+	
+	MySQLDumper uses a proprietary technique to avoid this problem. It only reads
+	and saves a certain amount of data, then calls itself recursively via JavaScript
+	and remembers how far in the backup process it was. The script then resumes
+	backing up from that point.
+	
+	The restore process is similar. Unlike other tools, splitting and splicing of
+	large backup files is no longer necessary.
+	
+	MySQLDumper can write the data directly into a compressed .gz file. The restore
+	script is able to read this file directly without unpacking it. You can also
+	use the script without compression, but using Gzip saves a lot of bandwidth.
+	You can even configure the script to automatically send the backup file to an
+	FTP account or your email adress. 
+
+  Download:
+    You can get the newest version at http://www.MySQLDumper.net/
+
+  Credits:
+    Please see http://www.MySQLDumper.net/credits/
+
+  Installation:
+    Please see the install_english.txt file.
+
+  Security:
+  	To protect MySQLDumper, you have to create a directory protection. Point your web
+  	browser to your MySQLDumper installation and push the button 'Create
+  	directory protection' (works only with apache) or create it manually
+  
+  Changelog:
+    Please see changelog_english.txt
+
+  Support:
+    See support forum under http://forum.MySQLDumper.de/
+    
+   Enjoy!
+    The MySQLDumper team