* bug#32845: guix.info: Missing manual
@ 2018-09-26 10:33 Pierre Neidhardt
2018-09-26 18:01 ` Ricardo Wurmus
2020-01-25 18:00 ` sirgazil via Bug reports for GNU Guix
0 siblings, 2 replies; 14+ messages in thread
From: Pierre Neidhardt @ 2018-09-26 10:33 UTC (permalink / raw)
To: 32845
[-- Attachment #1: Type: text/plain, Size: 105 bytes --]
The manual is missing from https://guix.info/manual/.
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#32845: guix.info: Missing manual
2018-09-26 10:33 bug#32845: guix.info: Missing manual Pierre Neidhardt
@ 2018-09-26 18:01 ` Ricardo Wurmus
2018-09-26 19:44 ` Pierre Neidhardt
2020-01-25 18:00 ` sirgazil via Bug reports for GNU Guix
1 sibling, 1 reply; 14+ messages in thread
From: Ricardo Wurmus @ 2018-09-26 18:01 UTC (permalink / raw)
To: Pierre Neidhardt; +Cc: 32845
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> The manual is missing from https://guix.info/manual/.
It’s actually available at https://guix.info/manual/en/ and
https://guix.info/manual/fr/.
The index is missing, though.
--
Ricardo
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#32845: guix.info: Missing manual
2018-09-26 18:01 ` Ricardo Wurmus
@ 2018-09-26 19:44 ` Pierre Neidhardt
2018-09-26 20:10 ` Ricardo Wurmus
0 siblings, 1 reply; 14+ messages in thread
From: Pierre Neidhardt @ 2018-09-26 19:44 UTC (permalink / raw)
To: Ricardo Wurmus; +Cc: 32845
[-- Attachment #1: Type: text/plain, Size: 185 bytes --]
Then we need to update the links on https://guix.info/help/.
I think the Savannah version is not in sync with those localized manuals.
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#32845: guix.info: Missing manual
2018-09-26 19:44 ` Pierre Neidhardt
@ 2018-09-26 20:10 ` Ricardo Wurmus
2018-09-27 13:46 ` Ludovic Courtès
0 siblings, 1 reply; 14+ messages in thread
From: Ricardo Wurmus @ 2018-09-26 20:10 UTC (permalink / raw)
To: Pierre Neidhardt; +Cc: 32845
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> Then we need to update the links on https://guix.info/help/.
> I think the Savannah version is not in sync with those localized manuals.
Indeed. The problem here is that the documentation is not actually part
of our website build. It is part of the GNU-hosted manuals.
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.
--
Ricardo
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#32845: guix.info: Missing manual
2018-09-26 20:10 ` Ricardo Wurmus
@ 2018-09-27 13:46 ` Ludovic Courtès
2018-09-27 15:28 ` Ricardo Wurmus
0 siblings, 1 reply; 14+ messages in thread
From: Ludovic Courtès @ 2018-09-27 13:46 UTC (permalink / raw)
To: Ricardo Wurmus; +Cc: Pierre Neidhardt, 32845
Hello,
Ricardo Wurmus <rekado@elephly.net> 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?
My initial plan was to use guix.gnu.org as the primary domain but we’re
stuck with the “Let’s Encrypt vs. multiple entries in DNS A records”
issue. At the same time, guix.info works just fine.
Thoughts?
Ludo’.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#32845: guix.info: Missing manual
2018-09-27 13:46 ` Ludovic Courtès
@ 2018-09-27 15:28 ` Ricardo Wurmus
2018-09-27 17:37 ` Pierre Neidhardt
2018-09-28 20:03 ` Ludovic Courtès
0 siblings, 2 replies; 14+ messages in thread
From: Ricardo Wurmus @ 2018-09-27 15:28 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: Pierre Neidhardt, 32845
Ludovic Courtès <ludo@gnu.org> writes:
> Hello,
>
> Ricardo Wurmus <rekado@elephly.net> 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’t know. I didn’t 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’re
> stuck with the “Let’s Encrypt vs. multiple entries in DNS A records”
> issue. At the same time, guix.info works just fine.
I thought the bigger issue was running a DNS server, which is something
I’ve never done and wouldn’t like to take on myself.
The problem with naive Let’s Encrypt updates is that automatic
challenges might fail when the “wrong” server is returned by the DNS
server. “certbot” 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’s Encrypt updates shouldn’t be a blocker.
--
Ricardo
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#32845: guix.info: Missing manual
2018-09-27 15:28 ` Ricardo Wurmus
@ 2018-09-27 17:37 ` Pierre Neidhardt
2018-09-28 20:08 ` Ludovic Courtès
2018-09-28 20:03 ` Ludovic Courtès
1 sibling, 1 reply; 14+ messages in thread
From: Pierre Neidhardt @ 2018-09-27 17:37 UTC (permalink / raw)
To: Ricardo Wurmus; +Cc: 32845
[-- Attachment #1: Type: text/plain, Size: 449 bytes --]
> 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.
This is crucial, I believe. I believe. "Static" documentation is a Bad Idea.
I think the manual is better than a wiki, but only if contributors can work on
it "live".
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#32845: guix.info: Missing manual
2018-09-27 15:28 ` Ricardo Wurmus
2018-09-27 17:37 ` Pierre Neidhardt
@ 2018-09-28 20:03 ` Ludovic Courtès
2018-09-28 20:38 ` Ricardo Wurmus
2018-09-28 20:39 ` Tobias Geerinckx-Rice
1 sibling, 2 replies; 14+ messages in thread
From: Ludovic Courtès @ 2018-09-28 20:03 UTC (permalink / raw)
To: Ricardo Wurmus; +Cc: Pierre Neidhardt, 32845
Hello!
Ricardo Wurmus <rekado@elephly.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
[...]
>> 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’t know. I didn’t 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.
Yes, it’s convenient.
>> My initial plan was to use guix.gnu.org as the primary domain but we’re
>> stuck with the “Let’s Encrypt vs. multiple entries in DNS A records”
>> issue. At the same time, guix.info works just fine.
>
> I thought the bigger issue was running a DNS server, which is something
> I’ve never done and wouldn’t like to take on myself.
I’ve never done it either :-) but our Knot service makes it looks easy.
> The problem with naive Let’s Encrypt updates is that automatic
> challenges might fail when the “wrong” server is returned by the DNS
> server. “certbot” 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 didn’t know about all this! Looks like our Certbot service doesn’t
support it though?
> I think the Let’s Encrypt updates shouldn’t be a blocker.
To me it was the main blocker.
Let’s see if we can bring more knowledgeable people on board…
Ludo’.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#32845: guix.info: Missing manual
2018-09-27 17:37 ` Pierre Neidhardt
@ 2018-09-28 20:08 ` Ludovic Courtès
0 siblings, 0 replies; 14+ messages in thread
From: Ludovic Courtès @ 2018-09-28 20:08 UTC (permalink / raw)
To: Pierre Neidhardt; +Cc: 32845
Pierre Neidhardt <mail@ambrevar.xyz> skribis:
>> 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.
>
> This is crucial, I believe. I believe. "Static" documentation is a Bad Idea.
> I think the manual is better than a wiki, but only if contributors can work on
> it "live".
One obvious problem with documentation on the web is that it’s hard to
tell if it matches the version of what you’re actually using. (That’s
one of the reasons for the “Documentation” section in the manual.)
The only reason IMO that justifies keeping “static” documentation (for
the latest release) is the installation instructions: these may change
anytime in ‘master’, but it’s important that those on-line match what
people will actually download.
Thoughts?
Ludo’.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#32845: guix.info: Missing manual
2018-09-28 20:03 ` Ludovic Courtès
@ 2018-09-28 20:38 ` Ricardo Wurmus
2018-09-28 20:39 ` Tobias Geerinckx-Rice
1 sibling, 0 replies; 14+ messages in thread
From: Ricardo Wurmus @ 2018-09-28 20:38 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: Pierre Neidhardt, 32845
Ludovic Courtès <ludo@gnu.org> writes:
>> The problem with naive Let’s Encrypt updates is that automatic
>> challenges might fail when the “wrong” server is returned by the DNS
>> server. “certbot” 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 didn’t know about all this! Looks like our Certbot service doesn’t
> support it though?
That’s right. The question is what we want to do in the auth hook when
this is performed in the service. We could just punt and have the user
supply the path to a custom hook script.
> Let’s see if we can bring more knowledgeable people on board…
Yes please! :)
--
Ricardo
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#32845: guix.info: Missing manual
2018-09-28 20:03 ` Ludovic Courtès
2018-09-28 20:38 ` Ricardo Wurmus
@ 2018-09-28 20:39 ` Tobias Geerinckx-Rice
2018-09-29 16:14 ` Ludovic Courtès
1 sibling, 1 reply; 14+ messages in thread
From: Tobias Geerinckx-Rice @ 2018-09-28 20:39 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: Pierre Neidhardt, 32845
Ludo', Guix,
Ludovic Courtès wrote:
> Ricardo Wurmus <rekado@elephly.net> skribis:
>> “certbot” 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 didn’t know about all this! Looks like our Certbot service
> doesn’t
> support it though?
Not out of the box, and last time I checked vanilla certbot didn't
provide an nsupdate (RFC2136) hook alongside all the DNSaaS API
rubbish.
But it's certainly possible, and wonderfully stable once set
up. t.gr runs entirely on GuixSD + Knot + DNS-validated LE certs.
Kind regards,
T G-R
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#32845: guix.info: Missing manual
2018-09-28 20:39 ` Tobias Geerinckx-Rice
@ 2018-09-29 16:14 ` Ludovic Courtès
0 siblings, 0 replies; 14+ messages in thread
From: Ludovic Courtès @ 2018-09-29 16:14 UTC (permalink / raw)
To: Tobias Geerinckx-Rice; +Cc: Pierre Neidhardt, 32845
Hi Tobias,
Tobias Geerinckx-Rice <me@tobias.gr> skribis:
> Ludovic Courtès wrote:
>> Ricardo Wurmus <rekado@elephly.net> skribis:
>>> “certbot” 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 didn’t know about all this! Looks like our Certbot service
>> doesn’t
>> support it though?
>
> Not out of the box, and last time I checked vanilla certbot didn't
> provide an nsupdate (RFC2136) hook alongside all the DNSaaS API
> rubbish.
>
> But it's certainly possible, and wonderfully stable once set up. t.gr
> runs entirely on GuixSD + Knot + DNS-validated LE certs.
Neat. Would you like to help come up with a Knot & Certbot config for
guix.gnu.org? :-)
The peculiarity is this:
--8<---------------cut here---------------start------------->8---
$ getent hosts guix.gnu.org
141.80.181.40 guix.gnu.org
185.233.100.56 guix.gnu.org
--8<---------------cut here---------------end--------------->8---
Ludo’.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#32845: guix.info: Missing manual
2018-09-26 10:33 bug#32845: guix.info: Missing manual Pierre Neidhardt
2018-09-26 18:01 ` Ricardo Wurmus
@ 2020-01-25 18:00 ` sirgazil via Bug reports for GNU Guix
2020-01-28 10:28 ` Ludovic Courtès
1 sibling, 1 reply; 14+ messages in thread
From: sirgazil via Bug reports for GNU Guix @ 2020-01-25 18:00 UTC (permalink / raw)
To: 32845
The "https://guix.info/manual/" currently redirects to "https://guix.gnu.org/manual/", which links to the manual in different languages.
Problem solved?
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#32845: guix.info: Missing manual
2020-01-25 18:00 ` sirgazil via Bug reports for GNU Guix
@ 2020-01-28 10:28 ` Ludovic Courtès
0 siblings, 0 replies; 14+ messages in thread
From: Ludovic Courtès @ 2020-01-28 10:28 UTC (permalink / raw)
To: 32845; +Cc: 32845, sirgazil
Hi,
sirgazil via Bug reports for GNU Guix <bug-guix@gnu.org> skribis:
> The "https://guix.info/manual/" currently redirects to "https://guix.gnu.org/manual/", which links to the manual in different languages.
>
> Problem solved?
I think so, thanks!
Ludo’.
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2020-01-28 10:29 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-09-26 10:33 bug#32845: guix.info: Missing manual Pierre Neidhardt
2018-09-26 18:01 ` Ricardo Wurmus
2018-09-26 19:44 ` Pierre Neidhardt
2018-09-26 20:10 ` Ricardo Wurmus
2018-09-27 13:46 ` Ludovic Courtès
2018-09-27 15:28 ` Ricardo Wurmus
2018-09-27 17:37 ` Pierre Neidhardt
2018-09-28 20:08 ` Ludovic Courtès
2018-09-28 20:03 ` Ludovic Courtès
2018-09-28 20:38 ` Ricardo Wurmus
2018-09-28 20:39 ` Tobias Geerinckx-Rice
2018-09-29 16:14 ` Ludovic Courtès
2020-01-25 18:00 ` sirgazil via Bug reports for GNU Guix
2020-01-28 10:28 ` Ludovic Courtès
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).