Hi people,
I'm working on HyperKitty, and I've understood that I need to add this
section to mailman.cfg to enable it :
[archiver.hyperkitty]
class: hyperkitty.lib.archiver.Archiver
enable: yes
base_url: http://hyperkitty.example.com
That works well. However, I need another key to
Why do you think that the configuration of HK should be a part of the MM core?
Like the Postorius configuration UI, HK is supposed to be a separable part of
the overall system which is possibly running on an entirely separate host
machine.
As such, its daemon would be configured and operated as
Why do you think that the configuration of HK should be a part of the MM core?
I didn't intend to put all of HK's config in mailman.cfg of course.
But I'm supposed to reference a class in the archiver.hyperkitty
section, which will be imported on startup, so it must be on the same
host.
Since
Sorry I messed up with a list-reply, so you people missed Richard's reply.
What concerns me is that MM core should not depend on Django in order to run.
The Archive interface needs to accept the message and place it in the store.
MM won't depend on Django, only if the HK section in mailman.cfg
You had mentioned a reference to the Django settings for HK.
Yes, my idea was to have something like that in the mailman.cfg file :
[archiver.hyperkitty]
enabled: yes
class: hyperkitty.archiver.Archiver
base_url: http://archives.example.com
conf_file: /path/to/django/app/settings.py
On Sep 13, 2012, at 04:53 PM, Aurelien Bompard wrote:
MM won't depend on Django, only if the HK section in mailman.cfg is enabled.
I can't just send the message to the store however, since the IArchiver
interface also has methods to get the list and message's final archive URL,
and that's
On Sep 13, 2012, at 10:37 AM, Richard Wackerbarth wrote:
The proper way to handle the issue of URLs would be to have the MM core query
the UI for them. However, I have yet to convince Barry that the present
model (where, at present, MM is the only part allowed to be authoritative
over ANY
On Sep 13, 2012, at 06:13 PM, Aurelien Bompard wrote:
Yes, my idea was to have something like that in the mailman.cfg file :
[archiver.hyperkitty]
enabled: yes
class: hyperkitty.archiver.Archiver
base_url: http://archives.example.com
conf_file: /path/to/django/app/settings.py
Only the
On Sep 13, 2012, at 04:07 PM, Aurelien Bompard wrote:
I didn't intend to put all of HK's config in mailman.cfg of course. But I'm
supposed to reference a class in the archiver.hyperkitty section, which will
be imported on startup, so it must be on the same host. Since there are
already
This is very interesting, thanks a lot for your suggestions.
If the base url is static, perhaps with some placeholders for list-specific
information, then the same approach used for mhonarc could be used for
hyperkitty.
That would work nicely for list_url() and permalink() indeed, even if it
On Sep 13, 2012, at 11:42 PM, Aurélien Bompard wrote:
True, but I still need to send the message to the store somehow.
Yeah, sorry I'm not familiar enough with HyperKitty to know how you get
messages *into* it. ;)
Cheers,
-Barry
___
Mailman-Developers
11 matches
Mail list logo
