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
|
# Radicale usage on a Debian system
Radicale can be started either in a user session or system-wide,
handling authentication itself or off-loading to a front-end service.
Radicale in Debian by default uses authentication scheme "remote_user",
i.e. expects a front-end service to resolve ${REMOTE_USER}.
## Apache via uWSGI with PAM authentication
Recommended setup for production use is to serve system-wide
by Apache via uWSGI with Apache-based authenticating.
Edit /etc/radicale/config to adapt as needed.
Install needed packages:
apt install uwsgi uwsgi-plugin-python3 apache2 libapache2-mod-authnz-external
Enable and activate back-end uWSGI service:
ln -st /etc/uwsgi/apps-enabled/ ../apps-available/radicale.ini
service uwsgi restart
Setup, enable, and activate front-end service:
a2enmod proxy_uwsgi
cp /usr/share/doc/radicale/examples/apache2-vhost.conf /etc/apache2/sites-available/events.example.org.conf
a2ensite events.example.org.conf
service apache2 restart
## Simple daemon
It should be possible to serve directly with sysV management,
although this is discouraged and not well tested.
Edit /etc/radicale/config to adapt as needed,
e.g. change in [auth] section to something else than "remote_user".
Activate init script:
update-rc.d radicale enable
## Limit memory consumption
When using uWSGI middleware with several threads or processes,
memory can be reduced at the expense of CPU use.
Edit /etc/uwsgi/apps-enabled/radicale.ini, enabling ksm.
Enable needed packages:
apt install sysfsutils
Activate detection and auto-merging of identical memory pages:
echo "kernel/mm/ksm/run = 1" >> /etc/sysfs.d/local-ksm.conf
service sysfsutils restart
service uwsgi reload
See /etc/uwsgi/apps-enabled/radicale.ini for other tuning opportunities.
-- Jonas Smedegaard <dr@jones.dk> Wed, 12 Dec 2018 15:51:06 +0100
|
