On Tuesday, August 26, 2003, at 11:00 AM, Frank Barknecht wrote:
> I guess, that most are running it on Linux. How about a poll?
There was a poll a little while ago that Chuck set up somewhere...
can't find it right now. Anyway, I seem to remember that Linux was the
> In general it seems, that a lot of Webware users simply create a
> with MakeAppWorkdir and then just work there, and as such don't really
> *need* ports (or rpms or debs or ebuilds). So no one did really care
> about a port. It's definetly not because Webware is crap. Plus:
> Webware itsekf has only one dependency and that it Python, so it's
> actually easy to install (not necessarily easy to set up, though)
I think there's a definite problem with Webware when it comes to system
administration and installation. It doesn't follow basic Unix
conventions, and it doesn't work well in that system. The
configuration is also a bit ugly. I actually started a couple days ago
to try to more or less rewrite (reread?) Webware to make it
distutilable, easier to configure, hopefully fast enough to use with
CGI (like OneShot), and unixify the paths (via configuration you could
of course still dump everything in one directory like it currently is).
And start using the logging module. Not really a rewrite, since I'm
trying to limit myself to these specific goals and not add other
features, but these changes touch all code and change the file layout
considerably. I'm hoping I can get it to the point where you can make
a directory that is your site root, and just do:
% cd path-to-your-root
And it would use /var/log/webware, /var/cache/webware,
/var/run/webware.pid, etc. (though actually with a second level to
support multiple webware application server processes) And for
installation just python setup.py install.
I'm not really sure how long this will take -- lots of little changes
required. But I think it would make Webware much easier to
administer, which would be great.