Could go past that error by adding the following in wsgi.py (as mentioned here <https://stackoverflow.com/a/5841964/1526703>)
sys.path.insert(0, os.path.abspath(os.path.join(os.path.dirname(__file__), "../../"))) sys.path.insert(0, os.path.abspath(os.path.join(os.path.dirname(__file__), "../"))) But cant see the Django site yet. Getting a 404. Perhaps I need to do the Virtual Host config anyways On Saturday, July 1, 2017 at 12:44:55 PM UTC+5:30, Anupam Jain wrote: > > First of all - thanks for mod_wsgi express! > > This <http://blog.dscpl.com.au/2015/04/introducing-modwsgi-express.html> > post says "As to the configuration of Apache, there actually wasn't any." > > *Is it ok to assume that I dont need to do any configuration on Apache at > all (as in nothing in conf-enabled/available and sites-enabled/available)?* > (That sounds to be too good to be true so thought to check) > > I have setup everything for mod_wsgi express and getting the error > "ImportError: > No module named '(projectname)'" > > This is not the one caused by circular imports but something to do with > setting the path somewhere I think (as I learnt from some SO posts) but not > entirely clear about it > > I did setup a django.conf in Apache's conf-enabled, so I am suspecting > that may be conflicting with something. > -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
