The main "feature" of web2py is that appliances are data and are treated as such. Consider a CMS app that wants to install, for example, a plugin. A plugin contains code and needs to be installable at runtime. The plugin may also modify other application files (such as replace a layout or a model).
This is the main distinctive feature of web2py vs other framework. This is what makes is work smoothly. I would not oppose to an external mechanism to locks/unlock *.py and *.html files for a certain app so that they cannot be modified by the www-data user while in production but one cannot break the internal directory structure of the apps without crippling it. Massimo On Mar 22, 6:55 pm, Dima Barsky <d...@debian.org> wrote: > Hi Mark, > > > Summary > > - The application under /var/web2py > > I disagree. Only the runtime data should go to /var, the code should > stay under /usr (and it should be immutable). I presume we are still > talking about pre-packaged applications, right? Nothing will stop > individual users from starting their own web2py instances with any > directory layout they want. > > I'm not the final authority on this matter, and I might be wrong with > my interpretation of the packaging guidelines. You can try asking for > advice on the debian-devel mailing list, but I think you'll hear the > same arguments from other debian developers as you've heard from me. > You could try convincing the debian community that this package is > important enough to make an exception from the rules. Good luck with > that. > > Again, I don't think this problem is specific to Debian. All > distributions try to separate code from runtime data, only some of > them are stricter than the others. > > Regards, > Dima. -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
