On 12/7/21 4:01 PM, David Newman wrote:
On 12/7/21 11:17 AM, Mark Sapiro wrote:
Add '127.0.0.1' to ALLOWED_HOSTS anyway.
Done, thanks.
Given that DNS works fine on this host, with localhost and 127.0.0.1 resolving backward and forward, this seems like a bug. Shouldn't the resolver be able to recognize localhost without hard-coding an address?
It's probably a bug, but if so, it's a Django bug and not anything Mailman can do anything about.
...
Assuming you have
STATIC_ROOT = '/opt/mailman/web/static'in your /etc/mailman3/settings.py file, you may need to create that directory if it doesn't exist. You shouldn't need to manually create the /opt/mailman/web/static/postorius directory if the /opt/mailman/web/static directory exists and is writable/searchable by the Mailman user.
Yes, that was it. Thanks.
Previously you'd pointed out what you considered an error in the venv docs, with the workaround to manually create the /opt/mailman/web directory [1]. I think the same issue applies here, and also that /opt/mailman/web and subdirectories need to be owned by the mailman user.
I don't recall what I said about that but near the end of the Initial Configuration section at https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configur... it says
Make sure that the logging path is created. You can run mkdir -p
/opt/mailman/web/logs to create the path.
I added
Also make sure the ``STATIC_ROOT`` directory is created.
after that.
As far as things being owned by the mailman user, early in the doc at https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-setup there is a note that says
Make sure that you are running commands as mailman user from here forth.
Setup Mailman user.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan