Annikka/evennia
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Some minor typos in game template

Browse source
This commit is contained in:
Griatch 2015-02-11 15:12:25 +01:00
parent 53a100fd33
commit f1b6a4e212
2 changed files with 13 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

23
evennia/game_template/README.md
View file

@ -1,22 +1,23 @@
# Welcome to Evennia! # Welcome to Evennia!
This directory is your game directory, set up to let you start with This directory is your game directory, set up to let you start with
your new game right away. your new game right away.
You can delete this readme file when you've read it and with the You can delete this readme file when you've read it and you can
exception of the `server/` directory you can, if you want, re-arrange re-arrange things in this game-directory to suit your own sense of
things in this game-directory pretty to suit your own sense of organisation (the only exception is the directory structure of the
organisation. See the readme's in each sub directory for more server/ directory, which Evennia expects). If you change the structure
information. you must however also edit/add to your settings file to tell Evennia
where to look for things.
Your game's main configuration file is found in Your game's main configuration file is found in
`server/conf/settings.py` (but you don't need to change it to get `server/conf/settings.py` (but you don't need to change it to get
started). If you just created this directory, `cd` to this directory started). If you just created this directory, `cd` to this directory
then initialize a new database using then initialize a new database using
evennia migrate evennia migrate
To start the server, `cd` to this directory and run To start the server, `cd` to this directory and run
evennia -i start evennia -i start
@ -24,12 +25,12 @@ This will start the server so that it logs output to the console. Make
sure to create a superuser when asked. By default you can now connect sure to create a superuser when asked. By default you can now connect
to your new game using a MUD client on localhost:4000. You can also to your new game using a MUD client on localhost:4000. You can also
log into the web client by pointing a browser to log into the web client by pointing a browser to
http://localhost:8000. http://localhost:8000.
# Getting started # Getting started
It's highly recommended that you look up Evennia's extensive It's highly recommended that you look up Evennia's extensive
documentation found here: https://github.com/evennia/evennia/wiki. documentation found here: https://github.com/evennia/evennia/wiki.
Plenty of beginner's tutorials can be found here: Plenty of beginner's tutorials can be found here:
http://github.com/evennia/evennia/wiki/Tutorials. http://github.com/evennia/evennia/wiki/Tutorials.

2
evennia/game_template/server/conf/settings.py
View file

@ -40,7 +40,7 @@ HTTP_LOG_FILE = os.path.join(LOG_DIR, 'http_requests.log')
# ENGINE - path to the the database backend. Possible choices are: # ENGINE - path to the the database backend. Possible choices are:
# 'django.db.backends.sqlite3', (default) # 'django.db.backends.sqlite3', (default)
# 'django.db.backends.mysql', # 'django.db.backends.mysql',
# 'django.db.backends.'postgresql_psycopg2' (see Issue 241), # 'django.db.backends.postgresql_psycopg2' (see Issue 241),
# 'django.db.backends.oracle' (untested). # 'django.db.backends.oracle' (untested).
# NAME - database name, or path to the db file for sqlite3 # NAME - database name, or path to the db file for sqlite3
# USER - db admin (unused in sqlite3) # USER - db admin (unused in sqlite3)