all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "jgart" <jgart@dismail.de>
Cc: "John Kehayias" <john.kehayias@protonmail.com>,  guix-devel@gnu.org
Subject: Re: Transformations Shell Syntax
Date: Sun, 16 Jul 2023 15:14:44 +0200	[thread overview]
Message-ID: <87a5vwuhff.fsf@gnu.org> (raw)
In-Reply-To: <07639ff5ed0060fc653c7d1b394ae88b@dismail.de> (jgart@dismail.de's message of "Mon, 03 Jul 2023 00:01:45 +0000")

Hi,

"jgart" <jgart@dismail.de> skribis:

> In other words being able to specify workers with shepherd:
>
> Starting multiple workers:
>
> $ herd start microblog-tasks@{1..4}
> $ herd status microblog-tasks@{1..4}
>
> Restarting a particular worker:
>
> $ herd restart microblog-tasks@3
>
> WDYT

I’ve never felt the need for this, and I’m typically not a “syntax
person” so to speak ;-), but *if* there is an actual need for this, then
we can thing about it.

(We might want to be more general though, like essentially allowing
users to apply an action such as ‘start’ to a set of services regardless
of their naming scheme.)

Ludo’.


  reply	other threads:[~2023-07-16 13:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23  6:43 Transformations Shell Syntax jgart
2023-05-23  8:16 ` Efraim Flashner
2023-05-23  9:39 ` Simon Tournier
2023-05-23 13:24 ` jgart
2023-05-23 13:55   ` Andreas Enge
2023-05-23 14:12   ` jgart
2023-05-23 14:22     ` Simon Tournier
2023-05-23 14:28     ` Andreas Enge
2023-05-23 17:20     ` jgart
2023-05-24  3:06       ` Ryan Prior
2023-05-26 15:50 ` Ludovic Courtès
2023-05-27 17:07   ` John Kehayias
2023-07-02 19:54     ` Ludovic Courtès
2023-07-05 20:23       ` John Kehayias
2023-07-03  0:01     ` jgart
2023-07-16 13:14       ` Ludovic Courtès [this message]
2023-07-23 13:00       ` Hartmut Goebel
2023-08-16 14:03         ` Ludovic Courtès

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=87a5vwuhff.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=jgart@dismail.de \
    --cc=john.kehayias@protonmail.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.