Sef, Miguel, I am very pleased to see you tackling this problem. Answers I received from elsewhere "oh, that's trivial..." were not at all helpful. Some web sites were helpful, but it was not always clear whether or not they were complete solutions. One comment (there might be more by now??) to the new book mentions complexity with newer Linux distributions or something. I should review that, but I'm on a roll :)
I think we should build some tools to capture the details, and I have been working toward that. The problem is complicated slightly by conflicting writings, and perhaps that the target moves over time. Another wrinkle for me is that I want https connections. Things I can offer, in varying stages of dis-repair: (1) OpenSSLCertificateFactory. I started this under Dolphin and was still thinking in Windows terms; I now consider Windows to be analogous to a draining wound in a part of my body I hope to keep. I still do some Windows-specific things, but the factory itself is designed to run on Linux; it would probably also be workable on a Mac, given its unix roots. I found openssl.exe to be slightly uncooperative. It would have been nice to have a library with entry points or at worst an executable willing to take arguments on the command line. All I could think to do was to create a configuration file with easily-recognized tags (e.g. COMMON_NAME) and to write a customized version of the file into a specified location with values provided as arguments to the method that does the work. I know I ran this on Linux at least once, but now I can't find all of the code (yet). It looks like it was one of my earlier efforts with SIF, which does not do a very good job with Dolphin's virtual categories, turning them into things that severely confuse Monticello, effectively unpackaging methods. The factory is really only of value to those wanting to self-sign a certificate. Some object mightily to this concept, but it works and it's FREE. I have no plans to make this work on Windows, because Linux shell scripting is remakably more rational than are Windows(TM) batch files. (2) Apacheat. (2a) This is something that I see as needing to work on Windows, since I do not (yet) expose Linux servers to the world. However, I have also reduced it to creating a batch file and a .reg file to configure a service (interestingly, that has broken AGAIN, this time on win2k3). It uses srvany (or whatever the correct name is) to run the vm as a service. Have I mentioned that I am tiring of Windows? (2b) It also has some code that iterates the Seaside apps and writes virtual host entries suitable for copying into an apache configuration file. The method in the new book might be simple enough to not bother with anything beyond a reference to where to find the relevant setup. Parts of the above depend on being able to get a fully qualified name for the local machine, and NetNameResolver is more than slightly broken in that area. I am convinced that it invokes primitives that are known to fail for IPv4 on IPv4 networks. I have something that appears to work on both systems on xp (perhaps IPv6) and 2k3 (IPv4). I need to try it again on Linux, and might soon have the ability to try Linux on another network - in fact my new discontinued $399.99 laptop is being delivered today. Tux and I are very excited. Having recently tried Vista for a few days, I plan to try to begin repartitioning this drive before Vista can so much as boot ;) Ok, maybe I should let it boot just to see if everything works; I'll think about it. Back to work. Bill -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Stéphane Ducasse Sent: Wednesday, September 23, 2009 12:22 AM To: [email protected] Subject: Re: [Pharo-project] Deploying Seaside: A tutorial Hi miguel Excellent! did you compare and check what we wrote on the seaside book? Stef On Sep 23, 2009, at 2:29 AM, Miguel Enrique Cobá Martinez wrote: > I have to written a tutorial about deploying Seaside applications to > production servers. The tutorial uses a simple application to test a > setup with following components: > > Debian GNU/Linux > lighttpd > Magma server > Magma seasideHelper > Seaside 2.8 > PharoCore > > You can find the tutorial here: > > http://miguel.leugim.com.mx/index.php/2009/09/18/deploying-seaside-app > lications/ > http://miguel.leugim.com.mx/index.php/2009/09/22/deploying-seaside-ins > tall-the-squeak-vm/ > http://miguel.leugim.com.mx/index.php/2009/09/22/deploying-seaside-pre > pare-the-images/ > http://miguel.leugim.com.mx/index.php/2009/09/22/deploying-seaside-pop > ulate-directories/ > http://miguel.leugim.com.mx/index.php/2009/09/22/deploying-seaside-con > figuring-the-webserver/ > > Hopefully this will add to the collective knowledge and will answer > some questions we all have had with respect to deploying Seaside. > There are a couple of post that I must write yet, the > SeasideProxyTester explanation and the load testing ones but you can > have a fully configured setup to try and adapt to your needs. > > Critics and comments are welcome. > > Cheers > -- > Miguel Cobá > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
