Charm: discourse
Summary
A platform for community discussion. Free, open, simple.
Charm Store
juju deploy cs:~marcoceppi/precise/discourse-14
Owner
marcoceppi
Maintainer
Marco Ceppi
Series
precise
Description
Discourse is the 100% open source, next-generation discussion platform built for the next 10 years of the Internet. Whenever you need a mailing list, a forum to discuss something, a chat room where you can type paragraphs, then consider Discourse.
Links
Repository   Bugs
lp:~marcoceppi/charms/precise/discourse/trunk
Interfaces
Provides
Requires
Config
admins string
Details
Readme
# About

This charm installs the Discourse application, http://discourse.org

# Install

After you've successfully bootstrapped an environment, run the following:

    juju deploy cs:~marcoceppi/discourse
    juju deploy postgresql

Then create relations

    juju add-relation discourse postgresql:db-admin

Discourse requires `db-admin` level access in order to enable the hstore
plugin. Finally, expose discourse:

    juju expose discourse

# Configure

There is currently only one configuration option for Discourse, this allows
you to set which user will be admin. To option takes a string of comma
separated usernames. You can find a username by visiting a user's profile
and copying the last part of the URL, in this case "marcoceppi": 
`http://meta.discourse.org/users/marcoceppi`. To set just one admin do the
following:

    juju set admins="marcoceppi"

Where "marcoceppi" is the username. For multiple admins use commas to
separate values:

    juju set admins="marcoceppi,codinghorror,sam,eviltrout"

In the event you wish to remove an admin, say `sam`, simply supply the
same list of users again only sans the user you wish to remove:

    juju set admins="marcoceppi,codinghorror,eviltrout"

If a user does not exist they will not be granted admin access and will
simply be skipped.

# Extras

These are additional things you can do to enhance your base install.

## Shared queuing server

If you have a need for a scaled out queuing server, or if you find yourself
with many discourse units, it will be beneficial to use a separate redis
server for queue management. To conserve resources all units, by default,
have their own `redis-server` installed. However, you can deploy and add
a relation to the [redis-master](http://jujucharms.com/charms/precise/redis-master)
charm in order to provide a central redis server.

    juju deploy redis-master redis
    juju add-relation discourse redis:db

In doing so the local `redis-server` installs will be removed and the site
re-configured to use the new redis service. For more information on scaling
out redis, refer to the [redis-slave](http://jujucharms.com/charms/precise/redis-slave)
charm.
Changes  
2013/02/27 Marco Ceppi Fixed Redis charm URLs (revno 27)
2013/02/27 Marco Ceppi Foreman now in upstream, use it for deployments (revno 26)
2013/02/27 Marco Ceppi Updated readme to reflect the CURRENT version of the charm (revno 25)
2013/02/27 Marco Ceppi Added secret_token generation for latest Discourse (revno 24)
2013/02/13 Marco Ceppi New upstart script, requiring foreman and a few work arounds (revno 23)
2013/02/13 Marco Ceppi Removing outdated upstart scripts (revno 22)
2013/02/08 Marco Ceppi Idempotency in db-relation-changed (revno 21)
2013/02/08 Marco Ceppi Added upgrade-charm (revno 20)
2013/02/08 Marco Ceppi Solid db creation, host_names is required, -W is dumb (revno 19)
Lint Check