> Can you elaborate on what your concerns are? If you were to install > apache2 outside OS X server, things get strange.
Apple declined support because the server was a 'non-standard' installation (I had more than one IP, set up as Apple's documentation showed).... I don't need to waste time with or any more hassle from Apple. > It can be trying, since most need better than the piss poor php it > comes with. I'm stuck with it. Period. > With ASSP, there is nothing OS X server has any interaction with. By > putting in a new perl, I have never had an issue, and I run software > update knowing when I open server admin tools, things will be just > how I left them. Default Server uses perl for other things. Apple has broken updated perl in the past (10.5.6, IIRC). It was their mistake, they even admitted it in print, but it caused not end of problems for those of us who had to back down to bootable archives of our startup disk. > But isn't that the crux of the problem? Apples perl is unarguably out > of date by some degree. Yep, but we live with it. For another week, anyway, until Snow Leopard is estimated to come out. Then we have to decide whether to run production servers with a v.0 OS.... > You add cpan modules into apples perl, software update comes along > and at least has opportunity to mess with > them. They don't always install properly, and even using then can cause problems (see above). > Even if you tell cpan to use something like /usr/local there have > been 1 or 2 times Apples stomped on that area in the past as well. At least minimising the sources of stomping, one can stand a better chance of keeping the box fully running. > What the method I am using does, is instal perl in /opt. Perl > modules too. ASSP is started with a full path to perl /opt/local/bin/ > perl assp.pl. There is no chance that ASSP is running with anything > outside of /opt. An interesting idea, but I admit that I've been burned more than once by Apple for not using their installed sw. :-/ > If you don't like it, rm -rf /opt and you are 100% back where you > were. You may have to dig out a launchd item, since those have to be > in Apples path. At least it's a simple method. :-) > I take this as far as installing all software in /opt. I don't want > Apples rsync, so I build it in /opt. One of the problems I've found with the various attempts like this is that some like /opt, some like /sw, some like .... It can get way too messy and confusing to know what has installed what, where. > MacPorts... Not a 100% mature project, but hands down the best > package manager I have used on OS X. Hands down the most amazing > support, they have helped me debug some of these SSL/TLS issues. I've used it in the past, but it was around at the time Apple support burned me. Then Apple messed up perl for those who had updated it. I've been burned too many times, so I have to be shy about messing with what has worked well in the past. > Too many variables, too many perl chained dependencies. A custom > test suite for ASSP that checks all perl modules would help this go > a long way. Oooooh, yep. :-) > I barely know perl well enough to even consider this idea. But right > now, it's far too random to troubleshoot in any meaningful way. assp is about as far as I want to go in CLI on my server. I have a real life and job. Just because some who use CLI find things easy does not mean that others want all that detail or power. Some just want a server to do the basic things and run stably: "I want this, so, click, I've set it on." For example, it's why Lingon is useful. Apple sells Server as a GUI-managed server. It is not, except for all but the most basic services. Some of us have other jobs that just need basic services for a small office and a small number of domains. Managing the server is the least of our worries. At least, it should be. The chasm between Apple's marketing image of the product and the product itself is one of the largest I've seen in 25 years in the sw business. :-/ Then there are all those 'open source' projects that constantly mention Win and Linux, but seem to constantly forget OS X Unix. "Easy install!" Not. => Frustration. T. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
