each app is running in an own instance with an own webserver and of course an own URL. But I cannot distinguish by the URL because this does not work for cron jobs.
I think the solution with reading a properties file and caching is fine for me. Still, I think this feature is necessary for almost every real world application and thus it would be good to have it in web2py. For example in java application servers you can configure db connections in the admin console and access them via jndi. In grails there is an own environment configuration so e.g. you can set different data sources, log settings and so on for testing, development and production environment (and of course you could use your own environment, e.g. customer specific). Alex Am Mittwoch, 4. April 2012 04:04:08 UTC+2 schrieb Anthony: > > thanks for the cache info. I think that's the way to go for me. I'll >> create a function to read the connection properties and add the cache >> decorator for the function. It is still just a workaround but at least it >> should not have any performance penalties. >> >> I'm still wondering why such an essential feature is missing... >> > > How do you know which customer is accessing the app -- does something in > the URL distinguish customers? Whatever it is, can't you just create a > dictionary mapping the relevant request parameter to the appropriate data > source URI and either keep that dictionary in a model file or import it > from a module? > > Anthony >
