1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
|
===========
Development
===========
Building documentation
======================
The full documentation is located in the "doc" subfolder. It can be generated
in various formats once you have installed `Sphinx`_. To generate the HTML documentation,
run the following command::
make -C doc html
The HTML files will be available in the ``doc/_build/html`` directory.
The documentation can also be browsed online at:
https://hyperkitty.readthedocs.org.
.. _Sphinx: http://sphinx-doc.org
Communication channels
======================
Hang out on IRC and ask questions on ``#mailman`` or join the `mailing list`_
``mailman-users@mailman3.org``.
.. _mailing list: https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Setting up HyperKitty for development
=====================================
The recommended way to develop on HyperKitty is to use VirtualEnv. It will
create an isolated Python environment where you can add HyperKitty and its
dependencies without messing up your system Python install.
First, create the virtualenv and activate it::
virtualenv venv_hk
source venv_hk/bin/activate
Then download the components of HyperKitty::
git clone https://gitlab.com/mailman/hyperkitty.git
cd hyperkitty
pip install -e '.[dev]'
.. include:: _sass.rst
Configuration
=============
For a development setup, you should create a file
``example_project/settings_local.py`` with at least the following
content::
DEBUG = True
TEMPLATE_DEBUG = DEBUG
USE_SSL = False
It's also recommended to change the database access paths in the ``DATABASES``
and ``HAYSTACK_CONNECTIONS`` variables. Absolute paths are required.
If you ever want to turn the ``DEBUG`` variable to ``False`` (by removing it
from ``settings_local.py``), you'll have to run two additional commands then
and each time you change the static files::
django-admin collectstatic --pythonpath example_project --settings settings
django-admin compress --pythonpath example_project --settings settings
Normally, to generate compressor content, you'll need to set ``COMPRESS_ENABLED`` to ``TRUE``
and ``COMPRESS_OFFLINE`` to ``TRUE`` in ``settings_local.py``. However, you can force the generation of
compressor content by adding the ``--force`` switch to the ``django-admin compress`` command, which
will run the compressor even if the ``COMPRESS`` settings are not ``TRUE``.
But for development purposes, it's better to keep ``DEBUG = True``.
.. note::
Your ``django-admin`` command may be called ``django-admin.py`` depending
on your installation method.
.. Setting up the databases
.. include:: database.rst
Running HyperKitty
==================
If you're coding on HyperKitty, you can use Django's integrated web server.
It can be run with the following command::
django-admin runserver --pythonpath example_project --settings settings
.. warning::
You should use the development server only locally. While it's possible to
make your site publicly available using the dev server, you should never
do that in a production environment.
Testing
=======
Use the following command::
django-admin test --settings hyperkitty.tests.settings_test hyperkitty
All test modules reside in the ``hyperkitty/tests`` directory
and this is where you should put your own tests, too. To make the django test
runner find your tests, make sure to add them to the folder's ``__init__.py``:
|
