On Sat, Dec 22, 2018, at 7:01 AM, brian@emwd.com wrote:
Hi Mark,
Merry Christmas (or Happy Holidays!).
I have the list settings set to Public archives and hyperkitty checked in the Active archivers box.
As for the cron jobs. I am not sure how to change the following to reflect my setup:
# This goes in /etc/cron.d/mailman
# Replace "apache" by your webserver user ("www-data" on Debian systems) and # set the path to the Django project directory
@hourly apache django-admin runjobs hourly --pythonpath /path/to/project --settings settings @daily apache django-admin runjobs daily --pythonpath /path/to/project --settings settings @weekly apache django-admin runjobs weekly --pythonpath /path/to/project --settings settings @monthly apache django-admin runjobs monthly --pythonpath /path/to/project --settings settings @yearly apache django-admin runjobs yearly --pythonpath /path/to/project --settings settings
- apache django-admin runjobs minutely --pythonpath /path/to/project --settings settings 2,17,32,47 * * * * apache django-admin runjobs quarter_hourly --pythonpath /path/to/project --settings settings
uwsgi handles all the cron jobs in the container images, you don't need to setup anything. See here1.
For instance, I am using nginx not apache. I also do not know what the /path/to/project should be using maxking's setup. I also am not sure how to call django-admin from the command line. I get the following:
# django-admin -bash: django-admin: command not found
If you do need to run django-admin commands, you have to do that
inside the container images. So, try this to enter the container:
$ docker exec -it mailman-web bash
Then to run commands:
$ python manage.py <subcommands>
-- thanks, Abhilash Raj (maxking)