On Tue, 28 Jul 2020 at 06:50, Mark Sapiro <mark@msapiro.net> wrote:
On 7/27/20 4:29 AM, Odhiambo Washington wrote:
On Mon, 27 Jul 2020 at 02:49, Mark Sapiro <mark@msapiro.net> wrote:
Is there an empty /opt/mailman/mm/__init__.py file?
No.
There has to be one. Create it and then Django will be able to import your settings.
See the first line after
Create directories: ... and files:
at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience#line-69
I don't know why I didn't see that initially :-)
Yes. However, that also means the /opt/mailman should be owned by mailman3, right? So I wasn't quite mistaken.
It doesn't matter what user actually
ownsthis directory and its subordinates as long as the Mailman user, mailman3 in your case, can read and write there. Of course, making everything owned by the Mailman user is the easiest way to ensure this.
True.
Note also that any commands in /opt/mailman/mm/bin need to be run as the Mailman user and not root. Running them as root can create things owned by root the can't be read by the Mailman user.
So, now I remember why I had to chown -R mailman3 /opt/mailman Then now it seems like I have been doing things incorrectly, because I have been doing a lot of operations as root by simply: cd /opt/mailman/mm virtualenv venv source venv/bin/activate Looks like the correct way is to start with su - mailman3
PS: There is the issue with qcluster, which doesn't seem to have been documented in details from your "experience". I see the configuration file and the init script, but not how to install it, or whether the procedure already installed it.
qcluster is part of Django. If you have this
# # Asynchronous tasks # Q_CLUSTER = { 'timeout': 300, 'save_limit': 100, 'orm': 'default', }
or similar uncommented in your Django settings, and also 'django_q' in your INSTALLED_APPS, it's there and all you need to do is run
/opt/mailman/mm/bin/django-admin qcluster
to run it, but it should be run as a service via init or ??
I have run it from supervisord. It has forked 30 processes and refuses to kill them when I stop supervisord. I will look for options around it.
Answering my own question I asked earlier, I have found "django-admin help --commands" to answer it.
PS: Did you by any chance find time to look into the issue about wsgi.py that you had mentioned - the one that has me stuck using it??
Thanks again.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)