From: Christian Laursen <xi@borderworlds.dk>
To: mlmmj@mlmmj.org
Subject: Re: List creation in the perl-admin web interface
Date: Wed, 22 Jun 2005 09:25:52 +0000 [thread overview]
Message-ID: <868y12kajj.fsf@borg.borderworlds.dk> (raw)
In-Reply-To: <86d5qekc0f.fsf@borg.borderworlds.dk>
Mads Martin Joergensen <mmj@mmj.dk> writes:
> * Christian Laursen <xi@borderworlds.dk> [Jun 22. 2005 10:54]:
>
> I've been wanting to rewrite mlmmj-make-ml anyway, making it possible to
> pass all options for making a list on the commandline. mlmmj-make-ml.sh
> is an ugly hack anyway--it was written pre-0.1.0.
Ah yes, I forgot about the requirement of a non-interactive mlmmj-make-ml.
> And when we have mlmmj-make-ml written proper, the rest seems
> achievable. Especially now we can write it with the above in mind.
>
> Any other considerations?
I have some ideas about what would be nice to have in the configuration file.
(Although it could be made possible to override those if running as root)
- Unprivileged users who are allowed to make lists (Perhaps just a group)
- Directories in which new listdirs are allowed to be created
- Allowed list domains
- Allowed prepopulated skeleton control dirs
- Allowed custom scripts to run after list creation
- Allowed listtexts directories
Some of this might work better if grouped in profiles.
Nothing more comes to mind at this time.
--
Christian Laursen
next prev parent reply other threads:[~2005-06-22 9:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 8:54 List creation in the perl-admin web interface Christian Laursen
2005-06-22 9:03 ` Mads Martin Joergensen
2005-06-22 9:12 ` Marcus Rueckert
2005-06-22 9:15 ` Mads Martin Joergensen
2005-06-22 9:25 ` Christian Laursen [this message]
2005-06-22 9:43 ` Christian Laursen
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=868y12kajj.fsf@borg.borderworlds.dk \
--to=xi@borderworlds.dk \
--cc=mlmmj@mlmmj.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.
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.