I don't think we were talking about using the built in server here.... just about setting up global variables per site vs. per application.
On Thu, Jul 23, 2009 at 4:46 PM, AchipA <[email protected]> wrote: > > Most non-hobbyist sites should not use the built-in server (yes, > that's an official recommendation), and with, say, apache+mod_rewrite > it doesn't matter anyway, right ? :) Enterprise does not mean one > should squander resources. On a double-quad core server I happen to > use at work, I use ~10 web2py processes and handle domain stuff > (whatever the count) on apache level and that turned out to work far > better than fiddle with routes.py or multiple web2py installs with 10 > processes of each to utilize the server. > > You seem to be making a web2py install=project=domain assumption, and > those equalities do not always hold, regardless of hobby or enterprise > use. > > And, as a closing thought, just because Django does something in a > certain way, it does not make it *automatically* the 'right and only > proper' way. > > On Jul 23, 8:40 pm, Bottiger <[email protected]> wrote: > > It is unreasonable because most non-hobbyist sites only have 1 > > canonical domain. When I run Web2Py it only uses around 20mb of memory > > for each instance. > > > > On Jul 23, 2:42 am, AchipA <[email protected]> wrote: > > > > > Unreasonable ? Why ? For example, I run several of my hobby projects > > > as separate web2py applications and all are on separate domains as > > > they are not really related (except for being done by me :) If I put > > > them on separate web2py instances, that would mean a tenfold memory > > > increase requirement for absolutely no gain at all. It's not any more > > > unreasonable to serve multiple domains as it is for web servers to do > > > so. > > > > > On Jul 23, 9:10 am, Bottiger <[email protected]> wrote: > > > > > > I think its safe to assume that one single copy of the web2py library > > > > serves a single domain. It works for Django. > > > > > > Serving multiple domains on a single Web2Py installation is an > > > > unreasonable configuration to support, and it should be split into 2 > > > > different Web2Py installations imo. > > > > > > On Jul 23, 12:02 am, Hans Donner <[email protected]> wrote: > > > > > > > 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 -~----------~----~----~----~------~----~------~--~---
