On 12/10/21 3:22 PM, David Newman wrote:
On 12/10/21 12:57 PM, Mark Sapiro wrote:
Are you using uwsgi or some other wsgi server.
uwsgi, per the venv and PDF docs. Thanks for the fix.
Regarding the uwsgi_pass docs, would 'uwsgi_pass_header' directives replace the 'proxy_set_header' ones in the venv doc?
Looking at the uwsgi doc, it seems they might do different things.
If you are using uwsgi and proxy_pass http://127.0.0.1:8000 is working for you, then I'm satisfied that the docs are OK now and we don't need to say anything about uwsgi_pass.
It's not the situation I have to deal with, though. Short of changing a long-standing URL, what I'm looking to do is have "/" continue to default to roundcubemail, and have users type in longer URLs for MM3 and other services.
I think you can set the document root to the roundcubemail root and then set locations for the Mailman destinations as, e.g.
location /mailman3/ {
proxy_pass http://127.0.0.1:8000;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $remote_addr;
}
location /archives/ {
proxy_pass http://127.0.0.1:8000;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $remote_addr;
}
location /accounts/ {
proxy_pass http://127.0.0.1:8000;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $remote_addr;
}
location /admin/ {
proxy_pass http://127.0.0.1:8000;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $remote_addr;
}
location /user-profile/ {
proxy_pass http://127.0.0.1:8000;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $remote_addr;
}I haven't tried anything like this, so I'm not sure it will work, but I think so.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan