diaspora, the privacy aware, personally controlled, do-it-all,
open source social network, is a decentralized social network
that puts you in control of you own data. When you set up a
personal pod, all your data is stored in that pod. You maintain
ownership of everything you share on diaspora, giving you full
control over how it's distributed.
diaspora* social network server. See more about diaspora* here -
Note! This version corresponds to diaspora* 0.5.99.x development version (ie the 0.6 dev branch). Not guaranteed to
work with older or newer major versions.
To install diaspora*, you will need to know the hostname that will be used.
Think carefully before installing, as this cannot be changed after installation.
To set the hostname, you will need to create a configuration file. At minimum
it needs the host name setting, but you can configure other parts of the
charm at the same time.
Note! While the hostname can be set after the initial deploy command - the
application will not be fully configured until a hostname is provided, so it is
wise to create a configuration file for the initial deploy command.
To deploy (from the Juju Charm store, once this lands there):
juju deploy --config=<path to config> diaspora
Until the charm is found in the charm store, deploy from a local repository. To
do this first create a path charms/trusty somewhere. Change to that path and
clone this repository. Create the config file and then:
juju deploy --config=<path to config> --repository=<path to charms/>
Currently Apache and Redis are installed inside the diaspora* container though
this will possible change.
If you didn't or forgot to set hostname during the deploy command, make sure to
set it before adding a db relation! Do:
juju set diaspora hostname="yourhostname.tld"
To deploy as localhost, Do:
juju set diaspora hostname="127.0.0.1"
If you don't already have one, you also need to deploy a database. Here we are
currently restricting ourselves to PostgreSQL.
To deploy just a plain database, you can do as follows:
juju deploy postgresql
Optionally add --to=0 to the command to deploy it to the Juju state machine.
Once services are deployed, create a relation with the database:
juju add-relation postgresql:db-admin diaspora:db
This will then trigger the actual building of the application - as it cannot be
fully completed without a database.
Important! Please note diaspora* takes a very long time to install, due to
the many Ruby gems that need to be pulled in. Depending on machine, this could
be from 5 to 30 minutes. Use juju debug-log to see the current progress. When
it is ready you will see Starting diaspora* server in the log as one of the
Starting diaspora* server
After everything is installed, you can expose:
juju expose diaspora
Note down the public address of the diaspora* service and check that it works.
See config.yaml for all options (link to file).
The only required (and not changeable afterwards!) option is hostname. Attempting to change the hostname afterwards will not take effect in the diaspora* installation.
A group of settings related to running backups of file uploads. See the Juju Backup charm and config.yaml for details. If the jujubackup charm is not installed, these settings have no effect.
To upgrade the diaspora* instance, you can use the following command:
juju action do diaspora/<unit> upgrade
<unit> = unit number of the diaspora service.
Discuss this charm in our Loomio diaspora*
Contact the charm author;
Please file bugs on GitHub. Pull
requests also welcome!
This charm is also on Launchpad, code
will be synced there from GitHub.
GNU General Public License v3 (GPL-3).
The author provides this charm as is and under no situation is responsible for
what it does or doesn't do.