On Jul 1, 5:52 pm, bruno desthuilliers <bruno.desthuilli...@gmail.com> wrote:
> That's what I understood, but I fail to see what made you think it > would be the case. It was what i implied when the app ran well on the machine that I had run the 'startproject' command on and didn't run at all on the one that i hadn't. I thought that perhaps one of the things startproject did was to add the directory to the sys.path. It was a reasonable conclusion, i think, just a faulty premise. excuse me if i hadn't done all my homework before starting to work on this. anyway, the first problem was that i hadn't added the entire path to the sys.path in the django.wsgi script, just the top of it, the cause of which was my own misinterpretation of a help page. The database problem was because the database's parent directory wasn't writable by apache. making the database file as well as its parent direcory writable by apache and running syncdb solved the database problem AND the admin problem, although i have to admit that i have no idea how it solved that (and it may be notable that the admin page works, just without any formatting. confusing but not entierly detrimental) as for running the app parallel to a static site, i had to change all the urls in all the templates and any pages referencing it to "/app/ myapp", as opposed to just "/myapp", where "/app" was the WSGIscriptalias. the weird url generation was because of a missing forward slash in the link on the template pages. again, both sorry and thanks. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
