Leo Famulari <[email protected]> skribis: > On Wed, Dec 02, 2015 at 10:07:23AM +0200, Ludovic Courtès wrote: >> David Thompson <[email protected]> skribis: >> >> > Looking for some feedback on my first stab at making the nginx service >> > extensible. With this extension mechanism, future web applications >> > (such as GNU MediaGoblin) that use nginx as a front-end web server will >> > be able to extend nginx with the server configuration that they need in >> > order to work. >> >> Excellent! >> >> > Here's a useless service that adds nginx configuration to serve the >> > contents of /tmp: >> > >> > (define server >> > (plain-file "foo.conf" >> > " >> > server { >> > listen 80; >> > root /tmp; >> > index index.html; >> > server_name dthompson.us; >> > } >> > ")) >> >> Do you think it would make sense to provide Scheme bindings for those >> ‘server’ configuration snippets, or would we lose too much >> expressiveness? > > I think you might lose too much, although I don't use GuixSD so I > don't know if there are other programs that are configured through > Scheme bindings. I know that I don't like the Nix bindings for systemd > in NixOS. They can't keep up with the pace of development in systemd and > provide a limited set of features.
Right, that’s exactly why I was asking: in some cases it’s OK to write bindings (they’re more convenient and just as expressive), but in other cases they’d be a loss, as you explain. Thanks for your feedback! Ludo’.
