NOTE: We are in the process of modifying the file structure and configuration for many Bitnami stacks. On account of these changes, the file paths stated in this guide may change depending on whether your Bitnami stack uses native Linux system packages (Approach A), or if it is a self-contained installation (Approach B). To identify your Bitnami installation type and what approach to follow, run the command below:
$ test ! -f "/opt/bitnami/common/bin/openssl" && echo "Approach A: Using system packages." || echo "Approach B: Self-contained installation."
The output of the command indicates which approach (A or B) is used by the installation, and will allow you to identify the paths, configuration and commands to use in this guide. Refer to the FAQ for more information on these changes.
You might want to extend the functionality of Discourse by installing a plugin. If you want to do this, you must get the repository URL for the plugin (where PLUGIN_REPO_URL is the URL to the repository of the plugin you want to install, like: https://github.com/discourse/discourse-akismet):
NOTE: If you connected to the instance via the Google Cloud Console, you will need to change your user to the bitnami user. Insert the following command before executing the steps below:
sudo su bitnami
Follow these steps below to install a new plugin:
Navigate to the Discourse installation directory. Depending on your installation type, run the commands below:
Approach A (Bitnami installations using system packages):
$ cd /opt/bitnami/discourse
Approach B (Self-contained Bitnami installations):
$ cd /opt/bitnami/apps/discourse/htdocs/
Next, install the plugin:
$ sudo RAILS_ENV=production bundle exec rake plugin:install repo=PLUGIN_REPO_URL
Finally, precompile new assets to be used by the plugin:
$ sudo RAILS_ENV=production bundle exec rake assets:precompile