unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Solène Rapenne" <solene@perso.pw>
To: Catonano <catonano@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: self hosting hardware
Date: Wed, 12 Jul 2017 11:06:44 +0200	[thread overview]
Message-ID: <980e9fd518b1f5bf7cb4397c39db8fcf@perso.pw> (raw)
In-Reply-To: <CAJ98PDyA=cZwtWc89h=fOCjE2LvpvG+UpunfefM7CP124i=SbA@mail.gmail.com>

Je 2017-07-12 09:19, Catonano skribis:

> In the next autumn/winter I would like to try to set up a self hosting 
> solution
> 
> And I'd love it to be GuixSD based
> 
> I need some help with selecting the hardware that fits the goal
> Hardware is not exactly my thing
> 
> A Beaglebone board (or equivalent) ? An Intel NUC (or equivalent) ?
> 
> It should probably serve a collection of static files over https, have 
> a smtp server and an IRC bouncher.
> 
> Optionally I'd like it to run some bittorrent or rsync or synchthing or 
> ipfs or DAT and a Gnunet node.
> 
> I'd love to be able to attach some external hard drives to it, both 
> traditionl hard drives and SSDs.
> 
> In the last few years the ADSL that serves my apartment has improved 
> dramatically
> 
> It used to be 300 Kb/s in upload for years
> 
> Now it's around 19 Mb/s
> 
> The optic fiber cord reached the cabinet just aside the building main 
> entrance
> 
> The copper fragment is now only a few meters.
> 
> So I could use some hardware suggestions to set up such a solution 
> based on GuixSD
> 
> It has to be cheap AND moderate in electricity consumption, possibly 
> like a home router (or something)
> 
> Thanks for any hint

Hello,

if you have some space and you are not afraid by noise, I would go for a 
homemade computer.
That would allow you to add network cards if you need and lot of hard 
drives.

If you go for a NUC or a mini-itx computer, that will not allow you to 
upgrade, and you may be limited to
1x 2.5" disk + 1x SSD in m3 format.

You just need :

- a processor (pentium/celeron, cheap and works well, and won't consume 
much)
- hard drive
- motherboard (you can by a cheap motherboard, look at the number of 
SATA ports)
- case (cheapest possible)
- power supply (buy a good one but not with a lot of power, 80+ 
standards can help to choose)
- 2x memory (2/4/8 Gb as you want)

  parent reply	other threads:[~2017-07-12  9:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-12  7:19 self hosting hardware Catonano
2017-07-12  7:22 ` Catonano
2017-07-12  8:03   ` ng0
2017-07-12  8:20     ` Rails Pjotr Prins
2017-07-12  8:47       ` Rails ng0
2017-07-14  9:42         ` Rails Ben Woodcroft
2017-07-12  8:53     ` self hosting hardware Catonano
2017-07-12 13:34       ` Ricardo Wurmus
2017-07-14  8:44         ` Catonano
2017-07-12  9:06 ` Solène Rapenne [this message]
2017-07-12 10:48   ` Catonano
2017-07-12 12:40   ` Pjotr Prins
2017-07-12 14:37     ` Solène Rapenne
2017-07-12 15:03       ` Vincent Legoll
2017-07-14  8:47         ` Catonano

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=980e9fd518b1f5bf7cb4397c39db8fcf@perso.pw \
    --to=solene@perso.pw \
    --cc=catonano@gmail.com \
    --cc=guix-devel@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).