unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jing <jing@jing.rocks>
To: guix-devel@lists.gnu.org
Subject: Re: Shutting down qa.guix?
Date: Thu, 14 Dec 2023 22:38:21 +0900	[thread overview]
Message-ID: <5494573c-fffd-4ff2-a2cd-65751047b2cb@jing.rocks> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1657 bytes --]

Hi everyone,

Forgive me for cutting in a conversation like this. I believe qa.guix 
can still be salvaged: I can host it per gratis, at least temporarily.

I am the admin of repo.jing.rocks, and I own the hardware. The servers 
are in my bedroom/living room. Adding qa.guix would cost nothing for me.

 > As for system administration, is there documentation that people 
willing to help could look at?  Very concrete things like: what services 
are running on which machines, what do I do if one of them is stuck or 
if I get this error message, etc.

Yes, docs are important, and I couldn't find one. What kind of spec does 
qa.guix require to keep operational? I see in the threads:

 > Storage is also an issue as beid currently is working with 340G of 
total storage and that's almost full [..]

I can spare a few terabytes of spinning rust storage. How about RAM and 
CPU? Does 64 vcpus (AMD EPYC 7773X) and 128GB RAM sound enough? If 
anyone wants to know to full spec, I can write it later.

Please note that the hardware I own requires non-free firmware, will 
this be a problem? Also, I'm not a good programmer, I can't maintain any 
package. I'm still learning Guile syntax and how to adapt to Guix. 
Someone else would have to work with me to keep the whole system going. 
Will this be an issue?


For the stability of repo.jing.rocks, please refer to [1] and [2]:

[1] https://mirror-master.debian.org/status/mirror-info/repo.jing.rocks.html
[2] https://archlinux.org/mirrors/jing.rocks/

-- 
Jing Luo
About me: https://jing.rocks/about/
PGP Fingerprint: 4E09 8D19 00AA 3F72 1899 2614 09B3 316E 13A1 1EFC

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

             reply	other threads:[~2023-12-15  0:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14 13:38 Jing [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-06 13:32 November/December update on qa.guix.gnu.org and related things Christopher Baines
2023-12-09 10:54 ` Shutting down qa.guix? Ludovic Courtès
2023-12-09 12:16   ` Christopher Baines
2023-12-09 13:30     ` Tobias Geerinckx-Rice
2023-12-10 10:54       ` Christopher Baines
2023-12-10 16:05         ` Maxim Cournoyer
2023-12-11 13:30           ` Christopher Baines
2023-12-10 18:50   ` Simon Tournier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5494573c-fffd-4ff2-a2cd-65751047b2cb@jing.rocks \
    --to=jing@jing.rocks \
    --cc=guix-devel@lists.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).