You know yo would be far better off having your yaml file (or the
definitions) defined
as an entity in the datastore and then you users could just upload new
versions

Which means you don't need to do deployments all the time

T

On Aug 8, 4:47 pm, VKM <vinaym...@gmail.com> wrote:
> Ok, its working now. Thanks Tim. I just put file along with other
> python files and it worked.
>
> Thanks,
>
> Regards,
> VKM
>
> On Aug 8, 1:41 pm, VKM <vinaym...@gmail.com> wrote:
>
> > Hi thanks for the reply.
>
> > I want my users to change the settings in yamlfile(like
> > settings.yaml) as and when they require and click on a button to let
> > us know that the user wants updates to be committed. Once that update
> > signal comes to us, a shell script can update the application on GAE.
>
> > Btw, I tried reading yamlfileusing open but I put thatfileinstaticfolder 
> > and it showed blocked error. Tim can you tell me where
> > this settings.yamlfileshould be stored? Should it be stored along
> > with other python scripts i.e. at root level? Could you please give
> > little more explaination.
>
> > Regards,
> > VKM
>
> > On Aug 7, 12:36 am, djidjadji <djidja...@gmail.com> wrote:
>
> > > the yamlfilemust be next to the python files and not marked asstaticin 
> > > app.yaml
>
> > > How do you want to let the client upload the yamlfile. If that is
> > > with an html form then you must store thefilein the datastore
>
> > > 2009/8/6 Tim Hoffman <zutes...@gmail.com>:
>
> > > > You can define you own yamlfile. and then read it directly (by the
> > > > way you can't from code, access
> > > > app.yaml or index.yaml)
>
> > > > Do something like this
>
> > > > from yaml import load
>
> > > > def loadSettings(settings='settings.yaml'):
>
> > > >    settings = load(open(settings,'r').read()))
>
> > > >    return settings
>
> > > > mysettings = loadSettings()
>
> > > > You probably want to cache this either in a module or memcache so you
> > > > don't have to reread it all the time.
>
> > > > Rgds
>
> > > > Tim
>
> > > > On Aug 6, 10:33 am, VKM <vinaym...@gmail.com> wrote:
> > > >> Hi
>
> > > >> Could you tell me then how to use my custom Yamlfilefor application
> > > >> settings? One simple way is to have a new pythonfilewith settings
> > > >> stored as dic or list etc and import it in main program. But that is
> > > >> not the good way. I want to give access of Yamlfileto my clients so
> > > >> that they can modify thefileand can update the content without
> > > >> worrying about Python code.
>
> > > >> Regards,
> > > >> VKM
>
> > > >> On Aug 4, 4:50 pm, djidjadji <djidja...@gmail.com> wrote:
>
> > > >> > You must not put this yamlfilein a directory forstaticcontent.
> > > >> > You can't open thesestaticfiles with python/java code
>
> > > >> > 2009/8/2 VKM <vinaym...@gmail.com>:
>
> > > >> > > Hi,
>
> > > >> > > I am writing a yaml configurationfilefor my application. This 
> > > >> > > config
> > > >> > >filewill contain fewstaticsettings (eg. drop down menu options). I
> > > >> > > may need to add or remove few options from the menu so in that 
> > > >> > > case I
> > > >> > > will just need to change my yamlfileand upload the app and changes
> > > >> > > will reflect.
>
> > > >> > > But when I read thefile, it gives error:filenot accessible. I saw
> > > >> > > the warning messages and it says: dev_appserver.py Blocking access 
> > > >> > > to
> > > >> > >staticfile...
>
> > > >> > > Can any body give me solution for this! How to read astaticfile,
> > > >> > > like a configfile. Do I need to do chances in my app.yamlfile?
>
> > > >> > > Thanks
>
> > > >> > > Regards,
> > > >> > > VKM
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to