Setting up Admin Account
So I installed a crontab for list and read about configuring the DB (I think I'll use SQLite). I got to http://docs.mailman3.org/en/latest/config-web.html . Because of the dollar sign, I assume that the commands are to be run as list. Here's what I did:
root@lists:~# ls root@lists:~# sudo list sudo: list: command not found root@lists:~# su list This account is currently not available. root@lists:~# ls /var/list ls: cannot access '/var/list': No such file or directory root@lists:~# locate mailman-suite_project root@lists:~# mkdir /var/list root@lists:~# chown list.list /var/list root@lists:~# su list This account is currently not available. root@lists:~# man su root@lists:~# su -s /bin/bash list list@lists:/root$ cd list@lists:~$ cd mailman-suite_project bash: cd: mailman-suite_project: No such file or directory list@lists:~$ mkdir mailman-suite_project list@lists:~$ cd mailman-suite_project list@lists:~/mailman-suite_project$ python manage.py createsuperuser python: can't open file 'manage.py': [Errno 2] No such file or directory list@lists:~/mailman-suite_project$ locate manage.py /usr/lib/python2.7/dist-packages/django/conf/project_template/manage.py /usr/lib/python2.7/dist-packages/django/conf/project_template/manage.pyc /usr/local/lib/python2.7/dist-packages/example_project/manage.py /usr/local/lib/python2.7/dist-packages/example_project/manage.pyc /usr/local/lib/python3.5/dist-packages/falcon/bench/dj/manage.py
Which manage.py should I use?
Pierre
Lanthanidia deliciosa: What the kiwifruit would be if it weren't so radioactive.
On 11/14/2017 08:13 PM, Pierre Abbat wrote:
So I installed a crontab for list and read about configuring the DB (I think I'll use SQLite). I got to http://docs.mailman3.org/en/latest/config-web.html . Because of the dollar sign, I assume that the commands are to be run as list. Here's what I did:
root@lists:~# ls root@lists:~# sudo list sudo: list: command not found
The command you want there is something like
sudo -u list bash
or whatever shell you want.
root@lists:~# su list This account is currently not available.
Probably because the default shell for list is nologin. But, I see you eventually figured it out.
root@lists:~# ls /var/list ls: cannot access '/var/list': No such file or directory root@lists:~# locate mailman-suite_project root@lists:~# mkdir /var/list root@lists:~# chown list.list /var/list root@lists:~# su list This account is currently not available. root@lists:~# man su root@lists:~# su -s /bin/bash list list@lists:/root$ cd list@lists:~$ cd mailman-suite_project bash: cd: mailman-suite_project: No such file or directory list@lists:~$ mkdir mailman-suite_project list@lists:~$ cd mailman-suite_project list@lists:~/mailman-suite_project$ python manage.py createsuperuser python: can't open file 'manage.py': [Errno 2] No such file or directory list@lists:~/mailman-suite_project$ locate manage.py /usr/lib/python2.7/dist-packages/django/conf/project_template/manage.py /usr/lib/python2.7/dist-packages/django/conf/project_template/manage.pyc /usr/local/lib/python2.7/dist-packages/example_project/manage.py /usr/local/lib/python2.7/dist-packages/example_project/manage.pyc /usr/local/lib/python3.5/dist-packages/falcon/bench/dj/manage.py
Which manage.py should I use?
Probably
/usr/local/lib/python2.7/dist-packages/example_project/manage.py
but your apparent lack of basic system administration skills is not making things easy for you. You might be better off looking at http://docs.list.org/en/latest/prodsetup.html#mailman-3-in-docker.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
list@lists:~$ cd mailman-suite_project bash: cd: mailman-suite_project: No such file or directory list@lists:~$ mkdir mailman-suite_project list@lists:~$ cd mailman-suite_project list@lists:~/mailman-suite_project$ python manage.py createsuperuser python: can't open file 'manage.py': [Errno 2] No such file or directory list@lists:~/mailman-suite_project$ locate manage.py /usr/lib/python2.7/dist-packages/django/conf/project_template/manage.py /usr/lib/python2.7/dist-packages/django/conf/project_template/manage.pyc /usr/local/lib/python2.7/dist-packages/example_project/manage.py /usr/local/lib/python2.7/dist-packages/example_project/manage.pyc /usr/local/lib/python3.5/dist-packages/falcon/bench/dj/manage.py
Which manage.py should I use? You are not supposed to create the directory mailman-suite_project but clone the mailman-suite project from gitlab and use it. None of the manage.py commands listed by your search are the right ones. The correct one is the one included in the repository of mailman-suite
On Friday, November 17, 2017 1:51:15 PM EST Simon Hanna wrote:
You are not supposed to create the directory mailman-suite_project but clone the mailman-suite project from gitlab and use it. None of the manage.py commands listed by your search are the right ones. The correct one is the one included in the repository of mailman-suite
It appears that setting up Mailman 3 requires knowledge of Django, which I don't have. I'm going to try something else.
Pierre
gau do li'i co'e kei do
Pierre Abbat writes:
On Friday, November 17, 2017 1:51:15 PM EST Simon Hanna wrote:
You are not supposed to create the directory mailman-suite_project but clone the mailman-suite project from gitlab and use it. None of the manage.py commands listed by your search are the right ones. The correct one is the one included in the repository of mailman-suite
It appears that setting up Mailman 3 requires knowledge of Django, which I don't have. I'm going to try something else.
You're welcome to do so since you know your needs better than we do, but please allow me to advise you that running Mailman 3 in most cases doesn't require knowledge of Django as long as (1) you follow the instructions *exactly*, and of course (2) assuming those instructions are correct.
Mailman 3 being just on the edge of becoming the industry standard for mailing list managers, yes, assumption (2) is occasionally violated. In my experience, (1) is a more frequent source of user troubles. Either way, we[1] are one heck of a lot faster at responding than most commercial and open source products when users have trouble. And we do have reason to lay claim to "industry standard".
Footnotes: [1] By "we" I really mean Mark Sapiro, Abhilash Raj, and off and on Simon Hanna. It's rare that it takes as much as 24 hours to get attention from one of them, and if Mark can handle it, usually you get an immediate solution. I haven't been able to keep up for months, but I hope to get back into the rotation soonish (in the new year).
-- Associate Professor Division of Policy and Planning Science http://turnbull/sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull@sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN
participants (4)
-
Mark Sapiro -
Pierre Abbat -
Simon Hanna -
Stephen J. Turnbull