Dear Ian, Thanks for the info, I've been messing with this and have some quesitons. From your example it seems that all of the WSCGI apps (or eggs really) need to be in the same folder, is that true? and if not what would be different if I wanted to revfer to an application which was not relative to my composit ini Jose Ian Bicking wrote: > jose wrote: > > > > Ben Bangert wrote: > > > > > >>App's can be mounted at specific points within the config ini file as > >>well. Here's an example: > >>http://pythonpaste.org/deploy/#applications > >> > >>Using this ability to load WSGI capable apps, I believe Ian Bicking > >>has even mounted an entire Django app under a section, as well as > >>TurboGears apps. If the forum of your dreams is in Django, the blog > >>you desire is in Pylons, and you want a TurboGears model browser; you > >>can bring that all together and run it. > >> > >>HTH, > >>Ben > > > > > > does anyone have a praticle example of the above they can post? This > > is the one aspect of WSCGI that I've been trying to figure out form the > > beginning and just don't get > > Well, the packages I've made (DjangoPaste and CherryPaste) have > frequently broken due to upstream changes, so in the specific case of TG > and Django it's not a stable situation. I haven't revisited Django > since magic-removal went live; hopefully it's actually better as a > result. Ideally what should happen in those packages go into the core > of their respective system with unit tests, and then they get updated. > They aren't intrusive (mostly), but most people inside those groups have > little active interest in integration. > > As it is, we do this at work a great deal, but all with Paste WebKit, > and occassionally some Wareweb stuff. And I'm sure Pylons would fit in > easily enough too. > > We have a single config file for each site that we call apps.ini. It > looks like: > > [DEFAULT] > (some global settings about where errors are emailed to, or things that > multiple apps are interested in) > > [composite:main] > use = egg:Paste#urlmap > > /app1 = config:app1.ini > /app2 = config:app2.ini >
> > And we have a line for each installed app, and a separate config file. > We also use a CGI/SCGI connector and Flup, and a ScriptAlias for each > URL we are mapping into Paste (i.e., ScriptAlias /app1/ > /path/to/cgi2scgi.cgi/). > > So when you access /app1, you ultimately get redirected to the WSGI > application object that app1.wsgiapp:make_app returns (exactly where > that entry point is depends on the framework and entry points and > whatnot -- it's looked up from information in the application's > setup.py). egg:Paste#urlmap is something that looks at the path and > redirects the request to the appropriate application based on that. So > everytime a request comes in, it gets redirected as necessary. > > Anyway, hopefully that helps some. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss -~----------~----~----~----~------~----~------~--~---
