Charm: roundcube
Summary
skinnable AJAX based webmail solution for IMAP servers
skinnable AJAX based webmail solution for IMAP servers
Charm Store
juju deploy cs:~nijaba/oneiric/roundcube-0
juju deploy cs:~nijaba/oneiric/roundcube-0
Owner
nijaba
nijaba
Series
oneiric
oneiric
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 string
db_persistent string
smtp_server string
smtp_user string
optimize_http int
smtp_pass string
do_https int
des_key string
default_port int
default_host string
ssl_crt string
use_https string
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, or that you 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. If you use the snake oil certificates at this time, you will not be able to do use 'add_unit' and load balance because each unit will have its own unique certificate/key. (Will be trying to solve this in a future version that will set a peer relation between member to share certificates.)
Changes
| 2011/12/10 Nick Barcet Default auto generated description had some unwanted bits (revno 20) |
| 2011/12/10 Nick Barcet Removing empty script (bug #795479 comment[5]) (revno 19) |
| 2011/12/10 Nick Barcet Modifying readme for snake oil cert (bug #795479 comment[3]) (revno 18) |
| 2011/12/10 Nick Barcet fixing type (bug #795479 comment[2]) (revno 17) |
| 2011/12/10 Nick Barcet Fixing start hook (bug #795479 comment[0]) Removing complexity in config-changed (bug #795479 commen (revno 16) |
| 2011/12/10 Nick Barcet loads of fixes after a few runs (revno 15) |
| 2011/12/10 Nick Barcet some refactoring to add optimize_http (revno 14) |
| 2011/12/10 Nick Barcet A bit more doc (revno 13) |
| 2011/12/10 Nick Barcet A little better error handling on restart-apache (revno 12) |
Lint Check
- err: Charms need a maintainer (See RFC2822) - Name <email>