I'll see both problems and another solution to work around this. We could install web2py into /usr/ directories with apt.
Then create a startup script that makes a copy of web2py and the web2py applications that are installed trough apt to the /var folder. A so called runtime version of web2py. We could let the script also take care of different users/password/ applications. Then i've one minnor question. Shall we keep the development versions of under var. Not best location, because var may get destroyed with an exception for /var/spool So Dima, do you know a place where we could put the applications imported through web2py mechanisme? regards Mark On Mar 23, 12:38 am, Dima Barsky <d...@debian.org> wrote: > > Where would you put php files? I have seen them in /var/www/ > > Massimo, > > I'm sorry to disappoint you, but any script you might've seen in /var/ > www was not underDebianpackage control, it was installed there > manually by the administrator. All php files are also installed under / > usr. If you try to create a package with script in /var most likely it > will not be accepted intoDebianfor the reasons I mentioned earlier. > I don't see any other way to make a clean package rather than put the > code and the runtime data into different directories. > > I still don't understand, what's wrong with a config file for each > application? This file would say whether the application is editable, > and where it's runtime files should be located. It the absense of > config file, it will default to the current layout, so the backward > compatibility is preserved. > > 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.
