-
Notifications
You must be signed in to change notification settings - Fork 16
Developer Troubleshooting
If you get an error about 127.0.0.1 not being free this means you probably closed the terminal window that you started up the web server in without actually killing the web server first. You need to kill the old web server process. On Mac OS X this can be done quickly and easily with Activity Monitor. Search for Python process, you should see one that has 14-15 threads. Kill this one by Force Quitting it.
You can always kill the server by the typing Control-C into the terminal window that you started the server up in.
This problem also arises from an improperly shut down web server. This means the server still has an old session. You can reset this by removing all session files from shiftspace/server/session/.
This probably means the underlying database design has changed. You will need to erase any and all ShiftSpace databases that were created in your CouchDB instance. Once you’ve done that you can recreate them from your ShiftSpace install directory with:
$ python shifty.py initdb
Often while you are working on the core HTML element of ShiftSpace you might accidentally write some malformed markup. ShiftSpace will not build with malformed markup. You will get an exception from CherryPy and a line number and column where the markup failed to validate. When this happens a file called error.html is written out to the tmp directory of your ShiftSpace repository clone. You can see the offending line there.