Renaming the default database file to evennia.db3 instead of evennia.sql, which is often used to signify text-based SQL dumps. Remember to re-name your database file and adjust your settings.py accordingly if you want to follow suite. Existing installs should theoretically be unaffected.

This commit is contained in:
Greg Taylor 2007-04-26 19:32:26 +00:00
parent 22bccd294f
commit c54f9f15e4
2 changed files with 3 additions and 3 deletions

View file

@ -10,7 +10,7 @@ ADMINS = (
MANAGERS = ADMINS
DATABASE_ENGINE = 'sqlite3' # 'postgresql', 'mysql', 'sqlite3' or 'ado_mssql'.
DATABASE_NAME = '/home/evennia/evennia/evennia.sql' # Or path to database file if using sqlite3.
DATABASE_NAME = '/home/evennia/evennia/evennia.db3' # Or path to database file if using sqlite3.
DATABASE_USER = '' # Not used with sqlite3.
DATABASE_PASSWORD = '' # Not used with sqlite3.
DATABASE_HOST = '' # Set to empty string for localhost. Not used with sqlite3.

View file

@ -20,6 +20,6 @@ mv $LOGNAME $LOGNAME_OLD
## Generate profile data for use with cProfile.
# $PYTHON_BIN -m cProfile -o profiler.log -s time server.py
## Interactive mode. Good for development and debugging.
# $PYTHON_BIN server.py
$PYTHON_BIN server.py
## Stand-alone mode. Good for running games.
nohup $PYTHON_BIN server.py > $LOGNAME &
#nohup $PYTHON_BIN server.py > $LOGNAME &