From: ludo@gnu.org (Ludovic Courtès)
To: Sohom Bhattacharjee <soham.bhattacharjee15@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: First installation - Questions
Date: Mon, 17 Jul 2017 11:57:19 +0200 [thread overview]
Message-ID: <87fudvbd34.fsf@gnu.org> (raw)
In-Reply-To: <d6ccba08-acad-2648-6870-58743cffead1@gmail.com> (Sohom Bhattacharjee's message of "Fri, 14 Jul 2017 13:10:44 +0530")
Hello,
Sohom Bhattacharjee <soham.bhattacharjee15@gmail.com> skribis:
> On 07/10/2017 03:14 PM, Ludovic Courtès wrote:
[...]
>>> 2. From reading the docs I figure that we are supposed to write
>>> config.scm for everything including web servers. This also means doing a
>>> `guix system reconfigure` after every change (even the trivial ones like
>>> setting up another virtual host etc). Is there any way I can *not* do
>>> this and run certain services like Apache or cron without declaring them
>>> in the config ?
>> You can always run them “by hand”, but then you don’t get the advantages
>> of using GuixSD.
>>
>> What makes you wary of running “guix system reconfigure”?
> After my second installation of Guix SD i changed a lot stuff in the
> config file and reconfigured but somehow that didn't work properly. So i
> ended up having to do single edits to the config and then running
> reconfigure after every edit. That worked nicely.
>
> Also I couldn't help but think that in GUIX we would need to have
> multiple declarations on the config for multiple virtual-hosts in nginx
> and other web servers. Right ?
Yes.
> This means we should run a guix system reconfigure even if we want to
> add another virtual-host.
>
> I'm not wary of "guix system reconfigure", it just feels "new".
>
> I guess I will have to ease into it. :-)
It sure feels different. :-) My recommendation would be to test new
configs with ‘guix system vm’ first. That allows you to figure out
obvious issues with service configs, etc.
Of course hardware-related issues can only be discovered when you boot
the config on the bare metal.
Cheers,
Ludo’.
prev parent reply other threads:[~2017-07-17 9:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-02 4:08 First installation - Questions Sohom Bhattacharjee
2017-07-02 19:15 ` Arun Isaac
2017-07-10 9:44 ` Ludovic Courtès
2017-07-14 7:40 ` Sohom Bhattacharjee
2017-07-17 9:57 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fudvbd34.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=soham.bhattacharjee15@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.