Ramon Diaz-Uriarte wrote: > Dear All, > > Pylons' documentation > (http://pylonshq.com/docs/0.9.3/getting_started.html#creating-a-pylons-project) > clearly explains the directory structure of a Pylons project. However, > as our applications are using some external applications, a few things > do not fit nicely in that directory tree. For instance, we have some > definition/configuration files used by LAM/MPI which are themselves > modified periodically by a script that checks which nodes are up; and > we have directories which store either temporal files or kind of > process counters. > > For now, we've been placing this under the "public" directory, with > appropriate subdirectories (e.g., lam-mpi-def-files; running-procs; > etc). But this does not really fit nicely with what I understand is > the purpose of that directory. > > Is it OK to create another directory at the same level as "public" for > this stuff? What is the most "Pylonesque" way of doing this?
My rule is that anything that goes in the directory structure should go into the version control system. It doesn't sound like those configuration files would be versioned, more like they are a form of communicating between the two systems. I'd put them in a different location (outside of the application directory structure) and point to them in the configuration file. -- Ian Bicking | [EMAIL PROTECTED] | http://blog.ianbicking.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
