Date: 07/22/01
- Next message: Dr Tarique Sani
email protected>>: "Re: [phplib] [RFC] Future of phplib" - Previous message: Dr Tarique Sani
email protected>>: "Re: [phplib] [RFC] Future of phplib" - In reply to: Dr Tarique Sani
email protected>>: "Re: [phplib] [RFC] Future of phplib" - Next in thread: Dr Tarique Sani
email protected>>: "Re: [phplib] [RFC] Future of phplib" - Reply: Dr Tarique Sani
email protected>>: "Re: [phplib] [RFC] Future of phplib" - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, 23 Jul 2001, Dr Tarique Sani <tarique <email protected>> wrote:
> On Sun, 22 Jul 2001, nathan r. hruby wrote:
>
> > I would think that php.net does it similarly, but I have no idea what they
> > use on the backend to make this happen for the website...
>
> Well I can politely ask the folks there and hope for the best.
We use a Jade/DocBook-based setup (also see the documentation
in [1]). One machine performs daily "builds" of the
documentation in various formats and copies it directly into
the rsync area. From there, it gets distributed to all
mirrors and the main web-site.
[1] http://viewcvs.php.net/viewcvs.cgi/phpdoc/
- Sascha Experience IRCG
http://schumann.cx/ http://schumann.cx/ircg
-- Abbestellen mit Mail an: phplib-unsubscribe <email protected> Kommandoliste mit Mail an: phplib-help <email protected>
- Next message: Dr Tarique Sani
email protected>>: "Re: [phplib] [RFC] Future of phplib" - Previous message: Dr Tarique Sani
email protected>>: "Re: [phplib] [RFC] Future of phplib" - In reply to: Dr Tarique Sani
email protected>>: "Re: [phplib] [RFC] Future of phplib" - Next in thread: Dr Tarique Sani
email protected>>: "Re: [phplib] [RFC] Future of phplib" - Reply: Dr Tarique Sani
email protected>>: "Re: [phplib] [RFC] Future of phplib" - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

