Glad to hear it's working so far.
One other thing that tends to confuse people when they're working on a Django website is the server side caching https://wiki.helionet.org/Django_on_HelioHost#WSGI_Uses_Server_Side_Caching What this means is if you visit your site, and then change some code, and then visit your site again, it's possible the changes appear or it's possible the old code still shows up. If you make multiple changes it's possible for multiple older versions of your code to continue showing up in the browser for up to 2 hours.
One way to deal with this is to make a change, and then wait 2 hours before you make another code change, and then wait another 2 hours to make the next change, etc. This is obviously a very slow process.
The other way to deal with this server side caching is to request WSGI restart access. If WSGI restart access is enabled you can clear the cache whenever you want so your code changes appear instantly. The downside to this though is your memory usage will be 260 GB per day, or more which means a bill of $1.91 per month or more. Let us know if you'd like to enable WSGI restart access so you can clear your server side cache.