L-electron-Rare/moodle
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Removed UPGRADING.txt (replaced by doc/upgrade.html) and updated README.txt

Browse Source 
to make it a bit clearer about where all the docs are.
This commit is contained in:
moodler
2002-10-29 03:52:10 +00:00
parent d6cd6ec4f6
commit a5d34d51cb
2 changed files with 11 additions and 93 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.txt
+11 -5
View File
@@ -1,8 +1,17 @@
README $Id$
------
Here is a basic outline of the installation process,
which normally takes me only a few minutes:
I highly recommend you read the detailed help on
installation, upgrading and use of Moodle, stored
in the doc subdirectory of this installation, or
read at:
http://moodle.com/doc/
For the impatient, here is a basic outline of the
installation process, which normally takes me only
a few minutes:
1) Move the Moodle files into your web directory.
@@ -24,9 +33,6 @@ which normally takes me only a few minutes:
6) Set up a cron task to call the file admin/cron.php
every five minutes or so.
For more details, I highly recommend you read the
full installation documentation, which is stored
in the "doc" directory or found at http://moodle.com/doc/.
Cheers!
Martin Dougiamas
UPGRADING.txt
-88
View File
@@ -1,88 +0,0 @@
UPGRADING $Id$
---------
As Moodle grows, there are changes to the code and
sometimes changes to the database structures.
Moodle is able to upgrade its own databases, using
information in files called version.php. There is
one of these for the main tables (in this directory)
and one for each module.
In the following instructions I will include some
sample Unix shell commands - there are obviously
graphical ways to do the same things.
Before the upgrade
------------------
Before upgrading any version of Moodle, I recommend
making a backup copy of the moodle directory, your
data directory and your database, to guard against
the very unlikely event that something in the upgrade
goes wrong.
At the very least, make a copy of your config.php file
and any languages, custom themes or plug-ins you have
added to Moodle.
Upgrading the files using CVS
--------------------------------
If you are using CVS, just go to the Moodle root
directory and update the files:
cvs update -dP
If you have been editing Moodle files watch the
messages very closely for possible conflicts
(and consider sending your fixes in to me as patches :)
Upgrading the files using a downloaded archive
-------------------------------------------------
Rename the current installation directory (as backup)
mv moodle moodle.backup
and then unpack the new tar or zip file into the old
location. DO NOT OVERWRITE AN OLD INSTALLATION
unless you know what you are doing - sometimes old
files can cause problems in new installations.
tar xvzf moodle-1.0.6.tgz
Next, copy the config.php file from your old installation
into the new installation (or make a new one by editing
config-dist.php). If you have created new themes or
other plug-ins then make sure you copy those back too.
cp moodle.backup/config.php moodle
cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme
Finishing the upgrade
---------------------
Visit the admin page of your installation to complete
the upgrade (eg http://example.com/moodle/admin).
It doesn't matter if you are logged in as admin or not.
Moodle will automatically detect the new version
and perform any database or filesystem upgrades that
might be necessary.
If all goes well (no error messages) then you can just
go on using the new version!
If you have problems with this procedure, let me know.
Cheers, and have fun!
Martin