Okay...quick update...getting better but still busted:
this is the contents of my django.wsgi file --
import os, logging, site, sys
site.addsitedir('/home/my-client/jht-commerce/lib/python2.5/site-
packages')
site.addsitedir('/home/my-client/jht-commerce/lib/python2.5/site-
packages/django')
LOG_FILENAME = '/var/log/wsgi.log'
logging.basicConfig(filename=LOG_FILENAME, level=logging.DEBUG)
sys.path.append('/home/my-client/jht-commerce/project')
sys.path.append('/home/my-client/jht-commerce/project/estore')
sys.path.append('/home/my-client/jht-commerce/lib/python2.5/site-
packages/Satchmo-0.9_pre-py2.5.egg')
logging.debug(sys.path)
os.environ['DJANGO_SETTINGS_MODULE'] = 'estore.custom_settings'
import django.core.handlers.wsgi
application = django.core.handlers.wsgi.WSGIHandler()
Now instead of getting a bunch of missing libraries (all the stuff in
egg files, etc) I'm getting the following error:
'AdminSite' object has no attribute 'urls'
Again, this whole thing runs just fine with ./manage.py runserver --
settings=custom_settings, its only when I make the move to mod_wsgi
where things start blowing up.
At first I was thinking it might have been a Solaris issue, but I've
in fact duplicated the problem(s) on my linux dev box.
I'm so lost as to how to get this to work...at one point I had an app
called "core" that didn't seem to work, renaming that app to something
else seemed to fix it, but then presented me with the AdminSite
error...
Its clearly a "path" of some sort that is messed up, but not sure
what.
On Sep 21, 10:37 pm, lifewithryan <[email protected]> wrote:
> Thanks Bob
>
> This is driving me nuts:
>
> the only thing that even comes close to working is removing the egg
> and symlinking to the appropriate library. however, anything
> installed via easy_install that leaves an egg, doesn't seem to get
> picked up.
>
> Example:
> in my django.wsgi script the only way I can get
> satchmo_store.shop.SSLMiddleware to show up is if I add the following
> line --
>
> site.addsitedir('/home/jht/jht-commerce/src/satchmo/satchmo/apps/')
>
> anyway, i'm about out of battery power and will probably be starting
> over from scratch tomorrow...perhaps forgoing easy_install all
> together, at this point i'm thinkin its an issue with easy_install and
> solaris...but I've no real way to know for sure.
>
> I'm losing my hair
>
> On Sep 21, 9:26 pm, Bob Waycott <[email protected]> wrote:
>
> > I can try to poke around our setup. We run our store on mod_wsgi, but as I'm
> > not the sysadmin, I don't handle that part of the job. I'll look into it and
> > try to get back with what I found as soon as possible.
>
> > On Mon, Sep 21, 2009 at 5:30 PM, lifewithryan <[email protected]>wrote:
>
> > > anyone here have experience getting satchmo to work on mod_wsgi --
> > > even better if they're running on joyent?
>
> > > from the command line, I can run the server and everything is found.
> > > but in my django.wsgi script I find i'm having to specify each egg
> > > individually. Is that right? Should I have to do that?
>
> > > I've got sys.path.append('path/to/project') and then a sys.path.insert
> > > (0, '/path/to/my/virtualen/site-packages/') but when I hit it via
> > > apache I get an Internal Server error and it can't seem to find the
> > > threaded_multihost middleware stuff, which happens to be in my site-
> > > packages as an egg.
>
> > > If i remove the egg and instead "link" to it -- its gets by that but
> > > then barks about satchmo_store SSLMiddleware.
>
> > > Any ideas as to what the heck I'm missing?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Satchmo users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/satchmo-users?hl=en
-~----------~----~----~----~------~----~------~--~---
