On Sun, 8 Sep 2002 10:50:34 -0700 [EMAIL PROTECTED] (Mike Orr) wrote: [...]
> > - Installing Webware involves calling install.py at its final location > > This and most of the other issues would be solved if we switch > to distutils as we have periodically discussed. > "python setup.py install" would install into the currently-running So is it worth trying to go for the distutil route in your opinion? I'm in the process of building an ebuild for a special app I have, and would like to incorporate an installation of Webware into it. I've been considering just creating a special install ebuild for my app ... since it is pretty special purpose, but I would prefer to create something that all Gentoo users could utilize to install Webware. I would prefer to always use mod_webkit, but that's just me. I've seen a great deal of email from many people that use, and want to continue using mod_python, and some just want to use OneShot. [...] > > - Which user should run the WebKit app server? Do you need a special > > user? What about multiple users each running an app server? I think > > there's no "best way" here, or rather, it depends on your needs. > > The distribution maintainer should specify it, allowing the sysadmin > to override. Some sites just use the same user their webserver is > running as. For more security, create a dedicated user. If a user > is taking responsibility for the appserver, he can run it under his > own login. As a final-final default, "nobody" (on Unix systems), > although that means "nobody" will own the files Webware creates > (*.pyc, log, session, error), and it's not great security-wise to allow > "nobody" to own files outside world-writeable areas. On the other > hand, the sysadmin had the opportunity to change it and neglected to, > so woe to him. How about using distutils to install Webware, and as part of the install process ( ebuild / bsd-port / deb-package? ) move / copy the default contexts to a /usr/local/WW or /usr/local/webware or /usr/local/WebWare or /usr/local/Webware directory created by MakeAppWorkDir. This would be the default contexts directory that would be used, and owned by the special user created by the ( ebuild / bsd-port / deb-package? ). [...] > > > - Startup scripts can vary across platforms, including between > > different Unix systems. Yes, but that's something that can get handled in the packaging ... tgz / ebuild / bsd-port / deb / rpm / open-ports / etc. There would need to be a maintainer(s) for each type of packaging. On the ebuild side I was looking to go with the cvs-eclass, and use that to just install from cvs, that way always have the latest based on a cvs-tag. In case you ever create 0.8.x style tags after the release of 0.8. This way people can get a branch that is stable, w/o having to go through a whole release process. Updating docs, and the like. Thomas: How far along are you? Are you working to make an ebuild based on release editions of Webware? or are you also looking at the cvs-eclass? Ray ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
