Re: Installation System Design for a Large Apache/mod

What I don't understand is why is it necessary to authomate all the installing.

Those troublesome authomatic installations come mainly from programs that are very expensive to be seen in intimacy.

So they have to be totally automatically installed, and if you don't have someone that pays you to study all the possibilities it would always fail somewhere.

But it would be better to do a simple form where people might fill in all the fields. Every field highly documented by some wiki at www. And some default values for people that might not be able to answer every question.

Then you have your desired installation and the rest would install well because the one that does the installation would be responsible of the results.

It would be helpful if there where some wiki: structured to answer questions about PM troubleshooting issues and related subjects.

Comment on Re: Installation System Design for a Large Apache/mod_perl Application

Replies are listed 'Best First'.
Re: Re: Installation System Design for a Large Apache/mod_perl Application by samtregar (Abbot) on Nov 17, 2003 at 03:30 UTC
What I don't understand is why is it necessary to authomate all the installing. I suppose it's not strictly necessary, merely highly desireable. There will always be a documented do-it-yourself method; it's the one that developers will use to bootstrap a CVS checkout into a working installation. But it will be much too hard for the average systems administrator to manage, requiring knowledge of Perl, Apache and database installation. The rest of your message made very little sense to me... What do you mean by 'seen in intimacy'? What do 'structured to answer questions about PM' have to do with this topic? -sam	[reply]

Replies are listed 'Best First'.

Re: Re: Installation System Design for a Large Apache/mod_perl Application
by samtregar (Abbot) on Nov 17, 2003 at 03:30 UTC

What I don't understand is why is it necessary to authomate all the installing.

I suppose it's not strictly necessary, merely highly desireable. There will always be a documented do-it-yourself method; it's the one that developers will use to bootstrap a CVS checkout into a working installation. But it will be much too hard for the average systems administrator to manage, requiring knowledge of Perl, Apache and database installation.

The rest of your message made very little sense to me... What do you mean by 'seen in intimacy'? What do 'structured to answer questions about PM' have to do with this topic?

-sam

[reply]