summaryrefslogtreecommitdiff
path: root/docs/MYSQL
diff options
context:
space:
mode:
Diffstat (limited to 'docs/MYSQL')
-rw-r--r--docs/MYSQL20
1 files changed, 10 insertions, 10 deletions
diff --git a/docs/MYSQL b/docs/MYSQL
index 1d5bcce3f..fe87e03fc 100644
--- a/docs/MYSQL
+++ b/docs/MYSQL
@@ -9,13 +9,13 @@ Introduction:
accessible on your website is still a great feature.
PHASE 1:Anope will be able to save all it's databases to MySQL. It will
- happen in conjuction with the current FFF databases. This first step is
+ happen in conjunction with the current FFF databases. This first step is
nothing more than a MySQL dump of the databases (i.e. read-only), since
Anope will not (for now) read from Mysql. (COMPLETED)
- PHASE 2:The next step is load the databases from mysql, being able to
+ PHASE 2:The next step is load the databases from MySQL, being able to
replace the FFF completely as an archive method (since all changes to
- the mysql db would be lost on the next Services save). All, while keeping
+ the MySQL db would be lost on the next Services save). All, while keeping
FFF intact. This is still not the final goal, but it's a milestone.
(COMPLETED)
@@ -26,13 +26,13 @@ Introduction:
PHASE 3:The next step, and most convoluted of all (since we'll need to
modify pretty much all the source) is to load/save (SELECT/INSERT) data
- in realtime. That way the mysql db could be modified externaly (web?).
+ in realtime. That way the MySQL db could be modified externally (web?).
Again, the FFF will be kept intact.
Requirements:
1. MySQL server version 3.23.32 or greater
- 2. MySQL libs and development files (usualy called mysql-dev).
+ 2. MySQL libs and development files (usually called mysql-dev).
3. A MySQL user account
4. A MySQL database
@@ -56,7 +56,7 @@ Configuration:
1. Run bin/mydbgen to help on the schema creation and adjustments.
- 2. Edit services.conf and add your mysql data to the MySQL configuration
+ 2. Edit services.conf and add your MySQL data to the MySQL configuration
block.
3. Start or restart services to make use of the new Anope executable.
@@ -65,7 +65,7 @@ Security:
To add a layer of security you have the option of encrypting or encoding
all passwords for nicks and chans. Use the "MysqlSecure" directive on your
- services.conf file to enable it. The availabe storage methods are:
+ services.conf file to enable it. The available storage methods are:
#MysqlSecure "" or MysqlSecure ""
@@ -74,8 +74,8 @@ Security:
MysqlSecure "des"
- Encrypts all passwords using a unix DES encription. This is a one way
- encryption algorithm. You can only validate it agains another DES
+ Encrypts all passwords using a UNIX DES encryption. This is a one way
+ encryption algorithm. You can only validate it against another DES
encrypted string, using the same "salt" (the first two characters of
the encrypted string). FAST
@@ -93,7 +93,7 @@ Security:
MysqlSecure "mykey"
Encodes the passwords using "mykey" as the encryption password. It
- produces a binary string and can be decoded using the MySQL builtit
+ produces a binary string and can be decoded using the MySQL built in
function DECODE(crypt_str,mykey). VARIABLE
Caveat: Keep in mind that this if you use any method other than clear