From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: bug#32845: guix.info: Missing manual Date: Thu, 27 Sep 2018 17:28:32 +0200 Message-ID: <87r2hfrmcf.fsf@elephly.net> References: <87y3bolf9v.fsf@ambrevar.xyz> <874lect9x0.fsf@elephly.net> <87efdgjb7h.fsf@ambrevar.xyz> <87zhw4rpel.fsf@elephly.net> <87ftxv3vf4.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49802) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g5YDy-0006nH-No for bug-guix@gnu.org; Thu, 27 Sep 2018 11:29:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g5YDu-0004pW-QK for bug-guix@gnu.org; Thu, 27 Sep 2018 11:29:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:52465) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1g5YDu-0004nk-7o for bug-guix@gnu.org; Thu, 27 Sep 2018 11:29:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1g5YDt-0003ML-VT for bug-guix@gnu.org; Thu, 27 Sep 2018 11:29:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: <87ftxv3vf4.fsf@gnu.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: Pierre Neidhardt , 32845@debbugs.gnu.org Ludovic Court=C3=A8s writes: > Hello, > > Ricardo Wurmus skribis: > >> The copy at guix.info does not use the same gnu.org/software/guix >> prefix, so all links to the manual are likely wrong. >> >> This needs to be fixed in our website code, so that the same code works >> for both sites. > > I wonder what should be done with guix.info: should we keep it as a > mirror, or should it redirect to gnu.org, or the opposite? I really don=E2=80=99t know. I didn=E2=80=99t plan for guix.info to become= popular, but it certainly is convenient right now as we can change DNS records at a whim. Currently, the manual shown on guix.info is fairly close to the latest in git. This means it contains documentation about channels, which cannot be found in the latest release that matches the manual on gnu.org. > My initial plan was to use guix.gnu.org as the primary domain but we=E2= =80=99re > stuck with the =E2=80=9CLet=E2=80=99s Encrypt vs. multiple entries in DNS= A records=E2=80=9D > issue. At the same time, guix.info works just fine. I thought the bigger issue was running a DNS server, which is something I=E2=80=99ve never done and wouldn=E2=80=99t like to take on myself. The problem with naive Let=E2=80=99s Encrypt updates is that automatic challenges might fail when the =E2=80=9Cwrong=E2=80=9D server is returned b= y the DNS server. =E2=80=9Ccertbot=E2=80=9D can be used with manual DNS validation, = which requires us to deploy a DNS TXT record. This can be automated with certbot hooks (scripts that have access to the token that should be published via environment variables) or through JSON mode, which returns an object with the token that can be processed through other means. I think the Let=E2=80=99s Encrypt updates shouldn=E2=80=99t be a blocker. -- Ricardo