Re: doc web efforts update
| From: | Nuno Lopes | Date: | Thu, 10 Jun 2004 10:09:36 +0000 |
| Subject: | Re: doc web efforts update | ||
| References: | 1 2 3 | Groups: | php.doc.web |
| Request: | Send a blank email to doc-web+get-18@lists.php.net to get a copy of this message | ||
> > * It uses lots of subdomains : $lang.$docteam.doc.domain.
> > (http://en.php.doc.keliglia.com/ for example)
> > I think this should be changed to something simpler, like:
> > docs.php.net/smarty/en/revcheck
> > »» /phpdoc/RFC
> >
> > (I suggested this way, but it could be anything else. I just don't
really
> > like to have thousands of subdomains)
> > This could be implemented using apache mod_rewrite, for example... What
do
> > you think of it?
>
> These thousands of subdomains are handled by PHP really (apache and the
> dns handle them as wildcards), so Mehdis code picks out the restricting
> selections from the domain name. It is similar to picking that out from
> the URL, but it does not need rewriting or 404 handling either. All the
> php.net project so far use URL path magic, and not domain name magic, so
> it might not be a good idea to break tradition here. But apart from
> this, I have no problem with using infinite subdomains. We are not in
> need of good pageranks :)
Yes I knew they were using dns wildcards. But search engines will not like
them :) (php.net has a pagerank of 10, so our subdomain will also have a
good PR :D)
I prefer using paths, but lets listen others' opinion.
> > Other thing:
> > To the RFC, TODO list, and in the future an on-line editing feature
(that
> > could be based on my project :-), I was thinking in using the php.net
magic
> > cookie to authenticate users. With this, the server would need to have a
> > copy of the password hashs of cvs accounts.
> > Your thoughts?
>
> I would love to see CVS user based authentication as already used on
> master.php.net, bugs.php.net, pear.php.net, etc.
Great! you agree with me. The bad part is that we need a copy of the
passwords of devellopers.
AFAIK, this is done by getting the /fetch/cvspasswd.php on the master
server. But we need the password :)
Of course they will not give us the password, so....
Gabor, me idea was: you talk with systems@ and ask for the password. Then
you would fetch the usernames/passwords to your pc. Then you would import
them to a sqlite DB and upload it to the server. That table would have also
the name, country, etc.. for each cvs account.
Nuno