On Tue, 2002-04-09 at 01:11, Terrel Shumway wrote: > On Mon, 2002-04-08 at 19:25, Ian Bicking wrote: > > On Mon, 2002-04-08 at 21:01, Terrel Shumway wrote: > > > * A wiz-bang GUI installer & launcher: > > > click, click, click, open browser > > > > I don't know this for a fact, but I imagine making a GUI Windows > > installer is similar to making the equivalent fancy Linux installer > > (which is an rpm/deb) -- and similarly, distutils is probably the key to > > doing it Right. > > Distutils does half of the job, and is OK for many purposes. My purpose > is to make a *braindead* installer:
I'm thinking that the installers use distutils to describe the package, and set up the installer. I haven't used these installers, this is just what I imagine. I know py2exe uses distutils. Just like with rpm/deb, distutils doesn't make it happen -- but it does bring you a whole lot closer. > * no python installation necessary That's hard... you'd have to install Python, but maybe as part of Webware -- something like py2exe doesn't make sense, since you aren't setting up an application, you are setting up a programming environment. I think it would be hard to make this any simpler or more robust than simply telling people to install some version of Python for Windows (of course, outside of Windows none of this installer stuff makes sense). > * no admin rights necessary > * no webserver necessary Doable with an embedded web server... Webware Experimental has one, I think...? (Also distutils) > * easy to setup multiple sites To the degree that setting up contexts could be easier, sure... that could even be done from the Webware admin screens. Virtual sites are more complex, and probably not quite so straight-forward that they are worth putting in the dead-simple installation. Separate AppServers are of interest, easy if the AppServer is a program, hard if it's a service. > * easy to clean up when you are done playing > > > Phase 2 (probably after 1.0) would be a set of management tools for a > real deployment: > * compile and install mod_webkit For Windows it would be precompiled. Installation should only mean copying, I think. > * install mod_rewrite rules? This is doable -- a simple query of where in the path Webware should go, and then set up the simple <Location /<user input>...</Location> could be put in. > * manage multiple webware "instances" > * start,stop,pause, configure service > * edit configuration > * add/remove/edit contexts/plugins > * load-balancing > * user name/passwords > * backup/restore > * manage log files > * manage error files Most of these could be added to the admin screens, so it would benefit all. Well, user handling isn't standardized so that wouldn't work. > * integration with boa-constructor What's that? I suppose this stuff should go on the Wiki at some point... Ian _______________________________________________ Webware-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-devel
