[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNUnet-developers] Revive doxygen on gnunet.org
From: |
xrs |
Subject: |
Re: [GNUnet-developers] Revive doxygen on gnunet.org |
Date: |
Sun, 7 Jul 2019 18:19:26 +0200 |
On Sat, 6 Jul 2019 14:24:53 +0000
address@hidden wrote:
> Christian Grothoff transcribed 4.2K bytes:
> > On 7/6/19 2:19 PM, address@hidden wrote:
> > > Christian Grothoff transcribed 3.2K bytes:
> > >> On 7/5/19 8:19 PM, xrs wrote:
> > >>> Hi all,
> > >>>
> > >>> I'd like to put doxygen again in place. I propose:
> > >>>
> > >>> 0. install a weekly cronjob for user doxygen and do "make full"
> > >>> in the respective folder.
> > >>
> > >> weekly is excessively slow, daily or hourly would be fine I
> > >> think.
> > >>> 1. Create two URLs
> > >>> a. https://docs.gnunet.org/handbook/
> > >>> b. https://docs.gnunet.org/doxygen
> > >>>
> > >>> Is this a good idea? I know it's not precise enough.
> > >>
> > >> I'd prefer to keep the full handbook under docs at the top-level
> > >> (also to avoid breaking links again!), and just do
> > >> doxygen.gnunet.org for doxygen.
> > >
> > > This is not what we have talked about in the beginning of the docs
> > > discussion. I don't expect you to remember this, but I think there
> > > are still open tickets which point out that this gathering of
> > > subdomains is a temporary state, and you even agreed that this is
> > > temporary. I mean we can
> > > still redirect with regexp, it's easy.
> >
> > Yes, but messy (to really capture all links) and slows down the
> > user, so we should avoid it if we can.
> >
> > > I would like to do what Taler
> > > did and use a docs landing page, and not have 1 new subdomain for
> > > every new feature which is related to text one can read. This will
> > > end up confusing people where to read about this.
> > > If you want the subdomains, the docs.* (or whatever) page can link
> > > to them, but outside of gnunet.org having a central landing page
> > > is good, having one toplevel subdomain for all of this would be
> > > better.
> >
> > Ok, but then we should change this ASAP and update the links (when
> > we originally discussed this, I also had not anticipated people
> > adding links to the handbook as quickly as it happened at the
> > GNUnet Hacker meeting...).
>
> Me neither, and that is good :)
>
> Maybe a task for the meeting in Berlin? The /docs/
> page in its raw form could be created in a couple of hours.
I'd like to do this as pronto as possible :) At the end of next week?
Here is the plan:
- on sam create different aliases in /etc/apache2/sites-enabled/docs-ssl
for docs.gnunet.org/<alias1|alias2|...> pointing to respective
folders
- install cronjob to do "make full" in /home/gnunet9/gnunet/doc
Okay? I'd need a helping root-hand ^^
cheers,
xrs
pgpNcbi97e56A.pgp
Description: OpenPGP digital signature
- [GNUnet-developers] Revive doxygen on gnunet.org, xrs, 2019/07/05
- Re: [GNUnet-developers] Revive doxygen on gnunet.org, Christian Grothoff, 2019/07/05
- Re: [GNUnet-developers] Revive doxygen on gnunet.org, xrs, 2019/07/05
- Re: [GNUnet-developers] Revive doxygen on gnunet.org, ng0, 2019/07/06
- Re: [GNUnet-developers] Revive doxygen on gnunet.org, ng0, 2019/07/06
- Re: [GNUnet-developers] Revive doxygen on gnunet.org, Christian Grothoff, 2019/07/06
- Re: [GNUnet-developers] Revive doxygen on gnunet.org, ng0, 2019/07/06
- Re: [GNUnet-developers] Revive doxygen on gnunet.org,
xrs <=
- Re: [GNUnet-developers] Revive doxygen on gnunet.org, ng0, 2019/07/07
- Re: [GNUnet-developers] Revive doxygen on gnunet.org, Christian Grothoff, 2019/07/07