10 Dec
2021
10 Dec
'21
8:57 p.m.
On 12/10/21 10:22 AM, David Newman wrote:
- At least on my system, the proxy_pass statement will only run without errors if I change this to a fully formed URL, e.g., 'proxy_pass http://127.0.0.1:8000'. Is this a typo in the docs?
I changed it at
https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configurat...
but I wonder if we shouldn't be using uwsgi_pass
instead of proxy_pass.
See https://nginx.org/en/docs/http/ngx_http_uwsgi_module.html#uwsgi_pass
Are you using uwsgi or some other wsgi server.
- What document root(s) and alias(es) to use for Postorius and Hyperkitty and the Django admin on a server that also runs other services (e.g., Postfix for non-list mail and Roundcubemail)?
If you can separate Mailman from other services by subdomain, you can configure them separately and for Mailman, root is irrelevant as everything is proxied or aliased in a location directive. For example, Mailman on the server that supports this list uses the lists.mailman3.org domain and we have (excerpted)
server {
listen 443 default_server;
root /usr/share/nginx/html;
index index.html index.htm;
# root and index are probably irrelevant as we never go there
server_name lists.mailman3.org;
ssl on;
#ssl stuff
location / {
proxy_pass http://127.0.0.1:8000/;
# other proxy stuff
}
location /static/ {
alias /var/spool/mailman-web/static/;
}
location /robots.txt {
alias /usr/share/nginx/html/robots.txt;
}
location /favicon.ico {
alias /var/www/listorg/images/favicon.ico;
}
}
And for the other stuff we have
server {
listen 443;
server_name .list.org mirror.list.org mirror.mailman3.org;
root /var/www/listorg;
ssl on;
# ssl stuff
}
--
Mark Sapiro <mark@msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan