unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: guix-devel <guix-devel@gnu.org>
Subject: Seeking "complex" system examples / guixops
Date: Mon, 29 Jul 2019 16:16:58 +0200	[thread overview]
Message-ID: <c7a55224-a352-7055-979b-faa96a377e60@crazy-compilers.com> (raw)


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

Hi,

now that guix deploy is making good progress, I wonder about "complex"
system examples, like setting up a full-stack nextcloud server.

For the background: I'm using debops [1] a lot, which is a collection of
integrated Ansible roles. For examples there are roles for setting up
ferm (an iptables firewall), nginx, php, databases and even
nextcloud/owncloud.

So for installing a nextcloud system including Lets' Encrypt
certificates, one only defines some variables and runs a prepared
Ansible playbook. The playbook will take care of passing variables
around from one role to another. E.g. nginx is configured to use an
"upstream" to php, which itself is configured to use the nextcloud code,
and the firewall is configured to allow port 80 and 443.

This not only installs the software and generates config files, but also
runs setups, generates passwords, initializes databases, etc.


So I'm wondering whether anyone is using guix for this kind of
system-setup in a flexible manner and whetehr one could share some examples.

Thanks in advance.

[1] https://debops.org

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |



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

             reply	other threads:[~2019-07-29 14:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-29 14:16 Hartmut Goebel [this message]
2019-07-29 15:53 ` Seeking "complex" system examples / guixops Ricardo Wurmus
2019-08-01 17:55   ` Hartmut Goebel
2019-08-01 18:13     ` Julien Lepiller

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=c7a55224-a352-7055-979b-faa96a377e60@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.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).