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
|
Juju charm Roundcube
author: Nick Barcet <nick.barcet@canonical.com>
Example deployment:
1. Setup your site specific parameters in roundcube.yaml
> vi roundcube.yaml
a list of all settable parameter with description is available using
> juju get roundcube
or listing config.yaml
2. Deployment with mysql and haproxy
>juju bootstrap
>juju deploy --config roundcube.yaml roundcube
>juju deploy mysql
>juju deploy haproxy
>juju add-relation mysql roundcube
>juju add-relation roundcube haproxy
>juju expose haproxy
3. Accessing your new roundcube site should be ready at
http://<haproxy-machine-addr>/. To find out the public address of haproxy,
look for it in the output of the 'juju status' command.
Note about HTTPS:
-----------------
to enable https access to your site, you can set "do_https" to the value of the
https port you want to listen to (443 is the default for https). You will
also need to provide the paths to *existing* SSLCertificate (ssl_crt) and key
(ssl_key). This means that you will have to use juju scp to upload your certicates
*before* making the config changes and adding other units.
You can also use the default ssl snake oil certificates provided by the ssl-cert
package:
# This config activates https on port 443
do_https: 443
ssl_crt: /etc/ssl/certs/ssl-cert-snakeoil.pem
ssl_key: /etc/ssl/private/ssl-cert-snakeoil.key
If the certificate you provide is invalid, apache will fail to load.
If the paths you provide are invalid, the https site will no be activated.
juju debug-log should be your friend, go have a look.
The certificates should be uploaded to the first unit you start, a peer relation
between all units will ensure that they will be reused identically everywhere.
|