Charm: roundcube
Summary
skinnable AJAX based webmail solution for IMAP servers
skinnable AJAX based webmail solution for IMAP servers
Charm Store
juju deploy cs:precise/roundcube-0
juju deploy cs:precise/roundcube-0
Series
precise
precise
Description
RoundCube Webmail is a browser-based multilingual IMAP client with an application-like user interface. It provides full functionality expected from an e-mail client, including MIME support, address book, folder manipulation and message filters. The user interface is fully skinnable using XHTML and CSS 2.
RoundCube Webmail is a browser-based multilingual IMAP client with an application-like user interface. It provides full functionality expected from an e-mail client, including MIME support, address book, folder manipulation and message filters. The user interface is fully skinnable using XHTML and CSS 2.
Hooks
Config
ssl_key string
smtp_port int
db_max_length int
force_https boolean
db_persistent boolean
smtp_server string
smtp_user string
optimize_http int
smtp_pass string
do_https int
default_port int
default_host string
ssl_crt string
use_https boolean
Details
Readme
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.
Changes
| 2012/03/22 Mark Mims config typing (revno 28) |
| 2012/01/28 Mark Mims wait for config:bool to land (revno 27) |
| 2012/01/28 Mark Mims strong config types (revno 26) |
| 2011/12/14 Nick Barcet forgot the protect the chmod if there is no certs (revno 25) |
| 2011/12/13 Nick Barcet better if I add the peer hooks to the branch.... (revno 24) |
| 2011/12/13 Nick Barcet send ssl cert keys via scp in peer relation (revno 23) |
| 2011/12/11 Nick Barcet no need to error out when it's too early to start (revno 22) |
| 2011/12/11 Nick Barcet * add peer relation between roundcube units * use peer relation to propagate des-key wich can now (revno 21) |
| 2011/12/10 Nick Barcet Default auto generated description had some unwanted bits (revno 20) |
Lint Check
- err: Charms need a maintainer (See RFC2822) - Name <email>