I found more than just the backend data-store varied accross production or local development (e.g. "reCaptcha account or not?", "sandbox charge processor, or real-put-this-stuff-in-my-bank-account charge processing"? .... dates, times, access to administrative testing, etc., etc.
I used a pretty low-tech variable in models/0.py that I called "DEV_TEST" --- and then used that item's setting in all the appropriate places. You could do this manually, or automagically (e.g. if request is for a localhost address, assume DEV_TEST is True). - Yarko On Sat, Oct 31, 2009 at 11:26 PM, Wiiboy <[email protected]> wrote: > > Hi guys, > I think I've finally decided that Web2py will be the framework I'll be > using for my site, because deployment onto my production server worked > great. > > Now, I can't figure out how to setup MySQL on my local computer, so I > use sqlite locally. But in production, I use MySQL. What's the best > way to determine if it's production or not? > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
