Re: HYPERKITTY_ATTACHMENT_FOLDER
Could You please confirm that this parameter should be placed in mailman-hyperkitty.cfg file? I have checked mailman/postorius/hyperkitty owner user can write files there and web user group has privileges to write and to read, but *no any files appear there*. Mailman works, it is possible to download attachments from hyperkitty. Mailman restarted, uwsgi restarted, runjobs restarted. No files in /full/path/to/folder/
File looks like:
[general] base_url: https://flistserv.example.com/hyperkitty/ api_key: BlaBlabla
HYPERKITTY_ATTACHMENT_FOLDER = /full/path/to/folder/
BR Ugnius
2019-09-11, tr, 21:21 Ugnius S <ugniusviln@gmail.com> rašė:
Thank You so much.
https://hyperkitty.readthedocs.io/en/latest/install.html Close to the end before the "UPDATE" topic, chapter "Customization".
https://buildmedia.readthedocs.org/media/pdf/hyperkitty/stable/hyperkitty.pd... Page 10, chapter 2.8 "Customization"
BR Ugnius
2019-09-11, tr, 20:16 Abhilash Raj <maxking@asynchronous.in> rašė:
On Wed, Sep 11, 2019, at 9:52 AM, Ugnius S wrote:
Hi.
Can anybody send example how to set it? It is mentioned in documentation, but very vaguely.
If you can point out where did you find it in docs, I can update it. Information is kind of duplicated in a few places.
HYPERKITTY_ATTACHMENT_FOLDER = /full/unix/path
This is the right value.
It is a path on the filesystem, where the user running Hyperkitty is allowed to write.
HYPERKITTY_ATTACHMENT_FOLDER = http://localhost:8000/something
HYPERKITTY_ATTACHMENT_FOLDER = ./var/data/something/
Has anybody experience of using this, maybe have recommendations of
it? Better under project user or better under web content owner where
using the
static content is. I would like to store attachments separately to avoid growing database. Hyperkitty documentation: By default, HyperKitty stores the email attachments in the database. If you would rather have them stored on the filesystem, you can set the HYPERKITTY_ATTACHMENT_FOLDER configuration value to a directory. Make sure that the user running the Django process (for example, apache or www-data) has the permissions to write in this directory.
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
On Wed, Sep 11, 2019, at 12:47 PM, Ugnius S wrote:
Could You please confirm that this parameter should be placed in mailman-hyperkitty.cfg file? I have checked mailman/postorius/hyperkitty owner user can write files there and web user group has privileges to write and to read, but *no any files appear there*. Mailman works, it is possible to download attachments from hyperkitty. Mailman restarted, uwsgi restarted, runjobs restarted. No files in /full/path/to/folder/
File looks like:
[general] base_url: https://flistserv.example.com/hyperkitty/ api_key: BlaBlabla
HYPERKITTY_ATTACHMENT_FOLDER = /full/path/to/folder/
No, this is supposed to go in your Django's configuration file, settings.py.
mailman-hyperkitty.cfg is used by Mailman Core to read config on how to archive emails in Hyperkitty. You need want to tell Hyperkitty to put attachments on disk and hence the changes are going to be "settings.py".
BR Ugnius
2019-09-11, tr, 21:21 Ugnius S <ugniusviln@gmail.com> rašė:
Thank You so much.
https://hyperkitty.readthedocs.io/en/latest/install.html Close to the end before the "UPDATE" topic, chapter "Customization".
https://buildmedia.readthedocs.org/media/pdf/hyperkitty/stable/hyperkitty.pd... Page 10, chapter 2.8 "Customization"
BR Ugnius
2019-09-11, tr, 20:16 Abhilash Raj <maxking@asynchronous.in> rašė:
On Wed, Sep 11, 2019, at 9:52 AM, Ugnius S wrote:
Hi.
Can anybody send example how to set it? It is mentioned in documentation, but very vaguely.
If you can point out where did you find it in docs, I can update it. Information is kind of duplicated in a few places.
HYPERKITTY_ATTACHMENT_FOLDER = /full/unix/path
This is the right value.
It is a path on the filesystem, where the user running Hyperkitty is allowed to write.
HYPERKITTY_ATTACHMENT_FOLDER = http://localhost:8000/something
HYPERKITTY_ATTACHMENT_FOLDER = ./var/data/something/
Has anybody experience of using this, maybe have recommendations of using it? Better under project user or better under web content owner where the static content is. I would like to store attachments separately to avoid growing database. Hyperkitty documentation: By default, HyperKitty stores the email attachments in the database. If you would rather have them stored on the filesystem, you can set the HYPERKITTY_ATTACHMENT_FOLDER configuration value to a directory. Make sure that the user running the Django process (for example, apache or www-data) has the permissions to write in this directory.
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
OK, I got it, resolved. I can confirm that adding this syntax line to /project/home settings.py or settings_local.py it works:
HYPERKITTY_ATTACHMENT_FOLDER = '/full/path/to/folder/'
Thank you Abhilash Kind regards Ugnius
2019-09-11, tr, 22:50 Abhilash Raj <maxking@asynchronous.in> rašė:
On Wed, Sep 11, 2019, at 12:47 PM, Ugnius S wrote:
Could You please confirm that this parameter should be placed in mailman-hyperkitty.cfg file? I have checked mailman/postorius/hyperkitty owner user can write files there and web user group has privileges to write and to read, but *no any files appear there*. Mailman works, it is possible to download attachments from hyperkitty. Mailman restarted, uwsgi restarted, runjobs restarted. No files in /full/path/to/folder/
File looks like:
[general] base_url: https://flistserv.example.com/hyperkitty/ api_key: BlaBlabla
HYPERKITTY_ATTACHMENT_FOLDER = /full/path/to/folder/
No, this is supposed to go in your Django's configuration file, settings.py.
mailman-hyperkitty.cfg is used by Mailman Core to read config on how to archive emails in Hyperkitty. You need want to tell Hyperkitty to put attachments on disk and hence the changes are going to be "settings.py".
BR Ugnius
2019-09-11, tr, 21:21 Ugnius S <ugniusviln@gmail.com> rašė:
Thank You so much.
https://hyperkitty.readthedocs.io/en/latest/install.html Close to the end before the "UPDATE" topic, chapter "Customization".
https://buildmedia.readthedocs.org/media/pdf/hyperkitty/stable/hyperkitty.pd... Page 10, chapter 2.8 "Customization"
BR Ugnius
2019-09-11, tr, 20:16 Abhilash Raj <maxking@asynchronous.in> rašė:
On Wed, Sep 11, 2019, at 9:52 AM, Ugnius S wrote:
Hi.
Can anybody send example how to set it? It is mentioned in documentation, but very vaguely.
If you can point out where did you find it in docs, I can update it. Information is kind of duplicated in a few places.
HYPERKITTY_ATTACHMENT_FOLDER = /full/unix/path
This is the right value.
It is a path on the filesystem, where the user running Hyperkitty is allowed to write.
HYPERKITTY_ATTACHMENT_FOLDER = http://localhost:8000/something
HYPERKITTY_ATTACHMENT_FOLDER = ./var/data/something/
Has anybody experience of using this, maybe have recommendations of using it? Better under project user or better under web content owner where the static content is. I would like to store attachments separately to avoid growing database. Hyperkitty documentation: By default, HyperKitty stores the email attachments in the database.
If
you would rather have them stored on the filesystem, you can set the HYPERKITTY_ATTACHMENT_FOLDER configuration value to a directory. Make sure that the user running the Django process (for example, apache or www-data) has the permissions to write in this directory.
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
participants (2)
-
Abhilash Raj -
Ugnius S