From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:55275) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i6gPM-0005zV-I3 for guix-patches@gnu.org; Sat, 07 Sep 2019 15:30:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i6gPL-0002QG-H5 for guix-patches@gnu.org; Sat, 07 Sep 2019 15:30:04 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:57506) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1i6gPL-0002QA-EW for guix-patches@gnu.org; Sat, 07 Sep 2019 15:30:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1i6gPL-0004G4-6D for guix-patches@gnu.org; Sat, 07 Sep 2019 15:30:03 -0400 Subject: bug#37320: [PATCH] hydra: dns: Add "data" to point at milano-guix-1. Resent-To: guix-patches@gnu.org Resent-Message-ID: References: <20190906114441.19067-1-mail@cbaines.net> <87sgp9axp8.fsf@gnu.org> From: Christopher Baines In-reply-to: <87sgp9axp8.fsf@gnu.org> Date: Sat, 07 Sep 2019 21:29:09 +0200 Message-ID: <878sqzc3cq.fsf@cbaines.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 37320-done@debbugs.gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Ludovic Court=C3=A8s writes: > Hi Christopher, > > Christopher Baines skribis: > >> * hydra/modules/sysadmin/dns.scm (milano-guix-1-ip4): New variable. >> (guix.gnu.org.zone): Add "data" to point at milano-guix-1, and update >> the serial. > > LGTM! Great, I've pushed this change now. >> Now that milano-guix-1 is back online, I'm interested in sorting out >> configuration for nginx, as well as letsencrypt for a TLS certificate. >> >> For that, it's probably useful to think about the DNS configuration. I >> think that this is something that has been discussed a bit in the past, >> but at that time there were some improvements I wanted to make before >> making anything more public. >> >> But, over the last month I've fixed some of the problems I knew about >> and added new features, so I'm happier at this point with it being more >> widely available. >> >> So, I've started looking at setting up the DNS configuration, and I've >> sent this patch which I think is the relevant change in the maintenance >> repository. > > Awesome. > > You can also add yourself an account in bayfront.scm (when the DNS is > hosted) so you can reconfigure, or I or someone else can reconfigure for > you. > > Let us know! So I've pushed the DNS change to the maintenance repository, and also added another change to for bayfront access. I guess someone will need to reconfigure bayfront before I can access it, there's no rush though, so no pressure. Thanks, Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEPonu50WOcg2XVOCyXiijOwuE9XcFAl10BQVfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNF ODlFRUU3NDU4RTcyMEQ5NzU0RTBCMjVFMjhBMzNCMEI4NEY1NzcACgkQXiijOwuE 9XcDzA//VUCRZKQAVbXhcPnlZrEyF8zt19ar3ckQ1SmN6IqFOPPLE0WTYioDWiJ5 VVxJpiomVHIV/dPTMjvNvYfYVxx6JOTG+RT0K09gonkM/CNUyz+ZMbq/KZOKV+LS +51CMX5SlUG/aPO9ElDoTFv+GQKdaeYGH+UJxm07qLQayUZ4Q0j7EsBq6/DphhvG Xo5rS3Oc5FFFqkCyBTbSzP7Y7iN97ykHCplE0u3VhbX7y6v0BlTWYrFrNvnTN+D3 eaXv3Or/qWekwwuhK3l+ZnZLaOa0/URwVQwReZshjL1nTbkuHM2cFoCJdTa+zXIj eKjFukyTnh5uoUNe/gwPJNw8vDmZVAxxz0fRSoTdaNUZXnw0HU4eLDrJlx+xp2mm qoe0u9WLZbrZpDubyl2PQarLPPd2ylyJKOF/TdXkpyzKHNucljEagI7IvSs1XK/x PufbHPH44BaQQshFNp63l4HJw8z4to8vyRE1X2tozy2tKL+MzV4KQ1FWup+NR1Oz Xxut4M7J+yliYwttmyXdv3BGbMJnKiw+iZIA3ZqusNWYtBOAQn81e/5Uu4MBDZws rHbrD/K5BL0pgrTPJ21kfLOlVrfGMOU2DUZpT8GNApPOv3UuoNI8TfnOgPSmLPNi tnebR8adXQ7L8bwHX91HGHRe72SqKdmlBi9noTTvplYw+iAPKvc= =hDpN -----END PGP SIGNATURE----- --=-=-=--