Currently the NOW install instructions suggest to install Evennia and then run evennia --init NOW. This will create the new empty game folder but it looks like NOW is itself distributed as a game directory already.
Here is a suggested alternative way for installing NOW with Evennia:
Install Evennia as normal, up to the point where the evennia command is working in your virtualenv.
git clone https://github.com/Pinacolada64/NOW.git (creates a new cloned NOW folder)
cd NOW
You already include the settings.py file in the repo, otherwise a user could do evennia --initsettings to create a new, empty settings.py in NOW/server/conf/ only for them.
evennia migrate
evennia start
(Also note that if using the settings.py file included in this repo one should change the SECRET_KEY string in it before it's used in a production server).
Currently the NOW install instructions suggest to install Evennia and then run
evennia --init NOW. This will create the new empty game folder but it looks like NOW is itself distributed as a game directory already.Here is a suggested alternative way for installing NOW with Evennia:
evenniacommand is working in your virtualenv.git clone https://github.com/Pinacolada64/NOW.git(creates a new cloned NOW folder)cd NOWsettings.pyfile in the repo, otherwise a user could doevennia --initsettingsto create a new, empty settings.py inNOW/server/conf/only for them.evennia migrateevennia start(Also note that if using the settings.py file included in this repo one should change the SECRET_KEY string in it before it's used in a production server).