unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>
To: Joshua Branson <jbranso@dismail.de>, raingloom <raingloom@riseup.net>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Easy DigitalOcean setup?
Date: Tue, 10 Nov 2020 00:02:37 +0100	[thread overview]
Message-ID: <72b1a59484e37185d18799f0c43227bee293e3f7.camel@korwin-zmijowski.fr> (raw)
In-Reply-To: <87pn4mf92n.fsf@dismail.de>

[-- Attachment #1: Type: text/plain, Size: 735 bytes --]

Le lundi 09 novembre 2020 à 17:40 -0500, Joshua Branson a écrit :
> You might try using a linode VPS.  That's what I'm using.  There is a
> guide in the cookbook that shows you how to set it up. :)
> 

Hey Raingloom !

I just played with Guix and DigitalOcean last couple of days.
If it's what you are looking for :

On my personal Ubuntu laptop, where I use Guix as a package manager, I
generated a compressed guix system image with :

$ guix system disk-image -t qcow2 do-conf.scm --image-size=5G

Then I uploaded the resulting image (i.e.
/gnu/store/f34vzy15zzk739l6gimkj5l4sn3brski-image.qcow2) as a custom
image on DigitalOcean.

Finally I create a droplet with this custom image and voilà !

Easy peasy.

Hope it will help!



[-- Attachment #2: do-conf.scm --]
[-- Type: text/x-scheme, Size: 875 bytes --]

(use-modules (gnu))

(use-service-modules ssh networking)
(use-package-modules screen ssh certs version-control)

(operating-system
 (host-name "doguix")
 (timezone "Europe/Paris")
 (locale "fr_FR.utf8")
 (packages (cons* screen git nss-certs %base-packages))
 (bootloader (bootloader-configuration
	      (bootloader grub-bootloader)
	      (target "/dev/vda")))
 (file-systems (cons (file-system
		      (mount-point "/")
		      (device "/dev/vda1")
		      (type "ext4"))
                     %base-file-systems))
 (services
  (append
   (list      
    (service dhcp-client-service-type)
    (service openssh-service-type
	     (openssh-configuration
	      (openssh openssh-sans-x)
	      (permit-root-login 'without-password)
	      (authorized-keys
	       `(("root" ,(local-file "/home/jeko/.ssh/id_ed25519.pub"))))
	      (port-number 2222))))
   %base-services)))

  reply	other threads:[~2020-11-09 23:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-09 22:28 Easy DigitalOcean setup? raingloom
2020-11-09 22:40 ` Joshua Branson
2020-11-09 23:02   ` Jérémy Korwin-Zmijowski [this message]
2020-11-10 18:39     ` David Dashyan
2020-11-10 18:47       ` Confusing typo (was: Easy DigitalOcean setup?) David Dashyan
2020-11-11 12:33         ` Efraim Flashner
2020-11-10  7:22 ` Easy DigitalOcean setup? Reza Alizadeh Majd

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=72b1a59484e37185d18799f0c43227bee293e3f7.camel@korwin-zmijowski.fr \
    --to=jeremy@korwin-zmijowski.fr \
    --cc=help-guix@gnu.org \
    --cc=jbranso@dismail.de \
    --cc=raingloom@riseup.net \
    /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.
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).