Thanks Jacob and Abhilash,
I've had enough of trying to do it myself so I've asked Brian (I'd previously asked him but he only does it on vanilla machines and I wanted to use an existing setup). I'll learn from his work once it is running and see what I can do without a migration deadline looming over me ;-)
Cheers,
Duane
On Wed, 24 Feb 2021 at 04:02, Abhilash Raj <maxking@asynchronous.in> wrote:
Hi,
On Tue, Feb 23, 2021, at 10:00 AM, duane@fairsay.com wrote:
Hi.
I've got a partial mailman3 install done and, based on the documentation, am not sure how to complete it! (this is my first time)
I've installed mailman3 (3.3.3) on a Debian 10 server using python3.7, mysql, postfix, apache, etc. and have run the install using pip3 install mailman. The "mailman info" command works, version shows "3.3.3 (Tom Sawyer)" the databases creates, tables, all exist, etc. So it seems the necessary services are running. I'm running froxlor on the server to configure the non-mailman services (apache, ssl, postfix, etc). I had also tried apt install mailman-full but it was an older version, so using the pypi route ensured I was on the latest version.
I don't know anything about Froxlor, so I won't be able to help with any issues caused due to that unfortunately.
Looking at https://docs.mailman3.org/en/latest/install/virtualenv.html, what I can't figure out is:
- There is no /opt/mailman/ user - the user installed seems to be "list"
The user recommended to create is "mailman" with "/opt/mailman" as the home directory for the user. Debian systems use the "list" user to run Mailman. You can simply substitute the user from mailman to list, the name itself doesn't make a lot of different, just make sure you do change the name in systemd config files and sudo commands that you use.
- Is a virtual environment needed for a production environment?
It is recommended by Linux distros that you don't install from pip directly into the system's site-packages. This can *potentially* have side effects and break other systems that rely on Python packages installed on your system, some which you might not even be aware of that relies on Python (like, Yum package manager does in RHEL systems).
Hence, if you aren't use the system packages to install Mailman, it is recommended that you use an isolated Python virtualenv.
- if django is setup properly or the webservice is working
- I've tried to connect to some web interface (posterious/hyperkitty/some mailman3 web frontend) via lynx to localhost:8001 on the local machine - but it has a 404 error
8001 is Mailman Core's API endpoint. To test Web Frontend, you want to reach out to: https://<mydomain>/ after configuring your Nginx to reverse-proxy the uwsgi.
Uwsgi runs a custom protocol, also called uwsgi, which Nginx understands and is able to reverse proxy. You can't use Lynx to test that. However, if you do want to test your service locally, you can add this line the uwsgi.init1 after the "uwsgi-socket" line:
http-socket = 0.0.0.0:8080This will make uwsgi also accept HTTP connections on Port 8080 that you can use to test.