On Wednesday, April 6, 2016 at 10:12:25 AM UTC-4, Fabiano wrote: > > What about files that don't fit any of those? > > I mean, I have private files, that are used directly by the developers or > production support staff, but not by the application itself, and I am not > sure where to put those. > > For example, application architecture diagrams, UML diagrams, requirements > and use case documents, specification of protocols, utility scripts to be > run by the server or by support staff on the server, shell scripts, etc. > > My first thought was the private folder, but it doesn't fit your > convention, as the app doesn't need those file (actually, it should > actually never directly access them). > > If there is not folder for such cases already, would you consider create > an additional empty folder in the scaffolding app and describe its purpose > in the docs? I guess having this as a convention would more interesting > than every developer doing this he's own way when needed.. >
Don't take that recommendation so literally. He was just indicating the /private folder is intended primarily for files that do not get sent over the network. They don't *have* to be used *by the application*. In any case, it's just a recommendation. You can put any files wherever works for you. You can even create your own additional sub-folders. Anthony -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
