release v1.0

git-svn-id: svn://presbrey.mit.edu/sql/mitsql@67 a142d4bd-2cfb-0310-9673-cb33a7e74f58

diff --git a/defaults.cfg.php b/defaults.cfg.php
index b8b68adab9c8989c22fe55b616a44f40dc9e0b7d..ae2efcbef5966dbe24862224b916b41f7361e518 100644 (file)
--- a/defaults.cfg.php
+++ b/defaults.cfg.php
@@ -16,8 +16,8 @@ $_NEW_USER['dCreated'] = 'NOW()';
 $_NEW_USER['bEnabled'] = 0;
 
 $_NEW_USERQUOTA['nDatabasesHard'] = 5;
-$_NEW_USERQUOTA['nBytesSoft'] = 49807360;
-$_NEW_USERQUOTA['nBytesHard'] = 52428800;
+$_NEW_USERQUOTA['nBytesSoft'] = 94371840;
+$_NEW_USERQUOTA['nBytesHard'] 104857600;
 $_NEW_USERQUOTA['dCreated'] = 'NOW()';
 
 $_NEW_USERSTAT['nDatabases'] = 0;

diff --git a/mitsql.cfg.php b/mitsql.cfg.php
index 5b69b6664a562971081dcc6236c6a7bc68245897..e2f44a56cf1a94129e7d3a01362015a94f4850eb 100755 (executable)
--- a/mitsql.cfg.php
+++ b/mitsql.cfg.php
@@ -11,7 +11,7 @@ file_exists('server.cfg.php') && require('server.cfg.php');
 defined('DEBUG') || define('DEBUG', 0);
 defined('DEVEL') || define('DEVEL', 0);
 
-define('VER', '0.3');
+define('VER', '1.0');
 if (DEVEL) {
        define('VERSION', VER.'-dev');
 } else {

diff --git a/tpl/index.php b/tpl/index.php
index 456d6e702342224070deae577092db32c1221533..8199e9335d176edcf8a255abb82ddc8bf7d1fcca 100644 (file)
--- a/tpl/index.php
+++ b/tpl/index.php
@@ -21,13 +21,13 @@ You may want to consider running scripts using the <a href="http://scripts.mit.e
 
 <p>
 All uses of this service must comply with the <a href="http://web.mit.edu/olh/Welcome/rules.html">MITnet rules of use</a>.
-The SIPB MySQL Service is part of the <a href="http://scripts.mit.edu/">scripts.mit.edu</a> service.
+The SIPB MySQL Service is part of the <a href="http://scripts.mit.edu/">scripts.mit.edu</a> project.
 </p>
 
 <h2>Backups</h2>
 
 <p>
-<strong>We strongly recommend you keep your own backups of your SQL schema and data. MySQL data is not stored in the AFS.</strong>
+<strong>We strongly recommend you keep your own backups of your SQL schema and data. MySQL data is not stored in AFS.</strong>
 Although we use various technical means to try to ensure the availability of your data (including hardware-level redundancy and real-time replication), we can make no guarantees about the reliability of the service and access to your data.
 <?/*
 As you work with your SQL data, it is automatically saved on an additional secondary SQL server for restoration in the event of a server failure.