Home > Archive > PHP Documentation > May 2004 > Re: [PHP-DOC] restructuring the install section
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: [PHP-DOC] restructuring the install section
|
|
| Nuno Lopes 2004-05-25, 12:34 pm |
| > Cheers,
>
> This is a long standing TODO item (dates back to at least January 2002 -
> the time of the install file split, but the install file split itself
> was done in the spirit of this TODO item :).
I love this spirit :) Finishing TODO items!!
The install part is completly outdated and really need lots of work.
I agree with your process to move the files. For me, lets start working!
But there is a problem... You are moving the files from one dir to another,
but now the install part is organized by server and not by operating system.
The content will have to change in this move.
And the ID's will be lost, too.
for example, we have "install.apache2" that will be splited? to
"install.win.apache2" and "install.nix.apache2"
> - move core configure options to an appendix (as was done with ini)
Totaly agree!
Nuno
| |
| Gabor Hojtsy 2004-05-25, 2:33 pm |
| > But there is a problem... You are moving the files from one dir to another,
> but now the install part is organized by server and not by operating system.
> The content will have to change in this move.
> And the ID's will be lost, too.
> for example, we have "install.apache2" that will be splited? to
> "install.win.apache2" and "install.nix.apache2"
The hard part in the installation is that we need to have advice for
multiple operating systems and multiple webservers. This sometimes
causes problems. Since the document format is only capable of having a
hierarhical TOC by nature, we need to decide on what will be the primary
indexing method for us: OS or server. Currently this is not really fixed.
I would prefer something like the current method, mostly indexed by
webservers, and only having the OS specific instructions separated when
needed.
Goba
| |
| Wez Furlong 2004-05-25, 2:33 pm |
| I generally agree, but think that all the windows stuff should be grouped
separately from the unixy platforms, as installation there is generally much
simpler (stick the binaries in one place and tweak a couple of config files).
+ Unixy Systems
+ Apache
+ ...
+ Windows
+ Apache
+ IIS 6 (Win2k3)
+ IIS 5 (Win2k / WinXP)
+ ...
I think it is also very important to stop telling people to put stuff in the
windows systems folders, as this just causes problems. I can go through the
win32 stuff once the restructuring is complete.
--Wez.
> -----Original Message-----
> From: Gabor Hojtsy [mailto:gabor@hojtsy.hu]
> Sent: 25 May 2004 18:14
> To: Nuno Lopes
> Cc: PHPdoc
> Subject: Re: [PHP-DOC] restructuring the install section
>
> dir to another,
> operating system.
>
> The hard part in the installation is that we need to have advice for
> multiple operating systems and multiple webservers. This sometimes
> causes problems. Since the document format is only capable of
> having a
> hierarhical TOC by nature, we need to decide on what will be
> the primary
> indexing method for us: OS or server. Currently this is not
> really fixed.
>
> I would prefer something like the current method, mostly indexed by
> webservers, and only having the OS specific instructions
> separated when
> needed.
>
> Goba
>
| |
| Gabor Hojtsy 2004-05-25, 3:33 pm |
| > I generally agree, but think that all the windows stuff should be grouped
> separately from the unixy platforms, as installation there is generally much
> simpler (stick the binaries in one place and tweak a couple of config files).
>
> + Unixy Systems
> + Apache
> + ...
> + Windows
> + Apache
> + IIS 6 (Win2k3)
> + IIS 5 (Win2k / WinXP)
> + ...
The problem is that the different Unix variants have different
instructions for Apache: HP-UX, Solaris, MacOSX. How do you think that
could fit in here? I don't know myself therefore I ask :)
> I think it is also very important to stop telling people to put stuff in the
> windows systems folders, as this just causes problems. I can go through the
> win32 stuff once the restructuring is complete.
Great. I planned to ask people to review the docs, as I also find it
silly to move stuff to the system folder, while it will work without it.
Also if the php.ini can be found in the php.exe folder in the first
place, why not tell people to put it there? It would be much easier to
install and remove. I have also planned on contacting server vendors to
help update the docs. The Sambar vendor added the right instuctions as
user comments on the sambar page for example.
Goba
| |
| Wez Furlong 2004-05-25, 3:33 pm |
|
>
> The problem is that the different Unix variants have different
> instructions for Apache: HP-UX, Solaris, MacOSX. How do you
> think that
> could fit in here? I don't know myself therefore I ask :)
Are they really all that different? If it's just a few minor differences,
then those things can be noted as subsections of the server docs:
+ Unixy
+ Apache
+ HP-SUX
+ Slowaris
Etc ;)
If there are a large number of differences for a given platform across the
different servers, it might well be worth giving that platform a section of
it's own at the same level as unix and windows docs.
> Great. I planned to ask people to review the docs, as I also find it
> silly to move stuff to the system folder, while it will work
> without it.
> Also if the php.ini can be found in the php.exe folder in the first
> place, why not tell people to put it there? It would be much
> easier to
> install and remove.
Yes, it's especially important to keep php.ini in the c:\php4 (or C:\php5 dir)
now that we are drawing close to a new major release.
> I have also planned on contacting server
> vendors to help update the docs. The Sambar vendor added the right
> instuctions as user comments on the sambar page for example.
That's good. I hope the others are helpful :)
--Wez.
| |
| Nuno Lopes 2004-05-25, 4:35 pm |
| > > > + Windows
[color=darkred]
> + Unixy
> + Apache
> + HP-SUX
> + Slowaris
Probably this is the best structure for the instal section.
Nuno
| |
| Gabor Hojtsy 2004-05-25, 4:35 pm |
| >>>>+ Windows
>
>
> Probably this is the best structure for the instal section.
OK. We can still keep the old manual IDs, unless someone would like to
add documentation for HP-UX, Solaris, or some other platform for a
non-Apache server. And unless we would like to clean up the ID structure
of the install section too (which might be desired :).
Goba
| |
| Friedhelm Betz 2004-05-25, 6:34 pm |
| On Tuesday 25 May 2004 20:09, Gabor Hojtsy wrote:
>
> The problem is that the different Unix variants have different
> instructions for Apache: HP-UX, Solaris, MacOSX. How do you think
> that could fit in here? I don't know myself therefore I ask :)
Looong time ago, I start playing around with the install files (but get
never done ;-( )
http://www.holliwell.de/installpart/v1/
Friedhelm
p.s.: the content is really a bit outdated as that version is one year
old ;)
| |
| Gabor Hojtsy 2004-05-25, 6:34 pm |
| >>>I generally agree, but think that all the windows stuff should be
>
> Looong time ago, I start playing around with the install files (but get
> never done ;-( )
> http://www.holliwell.de/installpart/v1/
>
> p.s.: the content is really a bit outdated as that version is one year
> old ;)
No problem, we can get the idea. Question is that Mac should be
separated from the Unix stuff or should be below it. I would probably
say: separate. But then again, it would be nice to have general stuff
for platform, and then server specific stuff (thus having the apache
quick ref under apache, and also the different unix stuff for apache
under apache if it does not differ much). I have quite adopted Wez's
outline :)
In case someone has time to code the orphan user note corrector
extension to /manage/user-notes.php, we can do this painlessly.
Goba
|
|
|
|
|