5 commits

Author	SHA1	Message	Date
Griatch	2b3a32e447	Reshuffling the Evennia package into the new template paradigm.	2015-01-06 14:53:45 +01:00
Griatch	bb36f2cb76	Changed to Django1.7. Django 1.6 no longer supported. To change, upgrade django to 1.7+ and then run manage.py migrate, possibly followed by manage.py migrate --fake for objects and players.	2014-09-17 10:49:42 +02:00
Griatch	0bf4f3cfea	Removed all old south migrations, leaving migration dirs empty for future django1.7 migrations.	2014-09-17 09:45:41 +02:00
Kelketek	89aebfc13f	Made migrations compatible with new user model when creating from scratch.	2013-07-20 15:45:16 -05:00
Griatch	9b9f90d91c	gtaylor convinced me to add migrations to the Evennia repo. This means that game/migrate.py is no more. The migrations will help you to adjust your database when Evennia releases a new database change, no need to drop the database or manually adjust tables. To make use of our schema migrations, you need to have Django-South installed. ... To convert to django-south operations, easiest is if you are willing to drop your old database (e.g. delete evennia.db if you use default sqlite3). Then do: "game/manage.py syncdb" followed by "game/manage.py migrate". That should do it. If you ever deletes your database, just rerun those two commands. If you want to convert an existing database, do game/manage.py convert_to_south comms game/manage.py convert_to_south config game/manage.py convert_to_south help game/manage.py convert_to_south objects game/manage.py convert_to_south players game/manage.py convert_to_south scripts In the future, you will then be able to do ./manage.py migrate when we tell you the schema has changed.	2011-03-21 00:53:58 +00:00