Be carefull with this. The same instance may serve on multiple domain names.... It's up to the developer to make these choices and decissions.
On Thu, Jul 23, 2009 at 07:20, Bottiger<[email protected]> wrote: > > Also a setting like this should be global to all applications while > stuffing it in a model will only apply to one application. So there > needs to be a global site-wide config just like routes.py. > > On Jul 22, 7:47 pm, Bottiger <[email protected]> wrote: >> Uhhh, so the solution is to make a file called 0.py in the models >> folder? This sounds very hackish. There should be an official way to >> do this. >> >> On Jul 22, 4:01 pm, Yarko Tymciurak <[email protected]> wrote: >> >> > yes - here's what you need to know: >> >> > every request that comes into the server, and then kicks off a we2py thread >> > starts in main.py, which parses and finds the appropriate applicaition, >> > controller and function being requested. Then, to set up the environment >> > for the request (so the controller can do what It needs, e.g. refer to >> > appropriate tables, have db connections available, etc.) main runs the >> > files in the application's model folder, and calls the appropriate >> > controller function with this environment. >> >> > Since the files in models are executed in alphabetical order, if you want >> > to >> > ensure that your "global" settings are available for the model files also, >> > a filename in controllers such as "0.py" or "0_setup.py" (that's a >> > zero) will accomplish this. >> >> > Hope this helps. >> >> > - Yarko >> >> > On Wed, Jul 22, 2009 at 5:18 PM, Bottiger <[email protected]> wrote: >> >> > > And that is my question. Where can I put it so it is a globally >> > > accessable variable? I don't think Web2Py has a global configuration >> > > file, or does it? >> >> > > On Jul 22, 3:05 pm, Fran <[email protected]> wrote: >> > > > On Jul 22, 11:01 pm, Bottiger <[email protected]> wrote: >> >> > > > > Its useful when you need the full URL. >> > > > > I needed this when getting Massimo's OpenID to work. Right now, its >> > > > > hardcoded in. >> >> > > > Well, there's no way that Web2Py can know what this is for sure as >> > > > there can eb proxies in front. >> > > > This is why it has to be edited manually for >> > > > auth.messages.verify_email: >> > >http://groups.google.com/group/web2py/browse_thread/thread/4887c684e5... >> >> > > > F > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
