On Dec 30, 6:46 pm, Adam <adam.crossl...@gmail.com> wrote: > Put it into your main Python source file.
Won't that cause data coherence issues? Whenever main.py is imported on a new server, it will assign values defined in the source code. Right? What if I want to change those values programatically? In some systems, such configuration data is stored in an INI file which is read/written by the admin interface. In GAE, we cannot access the file system so an INI file is out of the question. It seems that the datastore is the only place to put this info. It will essentially be a single-entity model. Thanks, Salman > > On Dec 30, 5:36 pm, slmnhq <salman....@gmail.com> wrote: > > > Hi, > > > Some applications have system variables like 'DEBUG_ENABLE', > > 'MAP_API_KEY', etc that can change the overall behavior of the > > application. > > > What is the best way to represent this data in our application? > > > One way to do this is have a module that exports this information as > > variables. This works fine if we never need to change this data at > > runtime. But what if an admin needs to change a system variable? > > > Is the answer here to use the datastore? How have other people done > > this? > > > Thanks, > > Salman --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
