Configure and enable Conpherence

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.

To enable Conpherence, follow these steps:

  • Install Node.js and npm (if not already installed) using the official installation instructions.

  • Set the Node.js environment variable:

      $ export NODE_PATH=/usr/lib/node_modules
  • Install ws globally:

      $ sudo npm install -g ws
  • Start the Aphlict service:

    • Approach A (Bitnami installations using system packages):

        $ sudo /opt/bitnami/phabricator/bin/aphlict start --config /opt/bitnami/phabricator/conf/aphlict/aphlict.default.json
    • Approach B (Self-contained Bitnami installations):

        $ sudo /opt/bitnami/apps/phabricator/htdocs/bin/aphlict start --config /opt/bitnami/apps/phabricator/htdocs/conf/aphlict/aphlict.default.json
  • Log in to Phabricator as an administrator and navigate to the “Configuration -> Core Settings -> Notifications” section.

  • Modify the notification.servers value by entering the following configuration, ensuring the IP-ADDRESS placeholder reflects the IP address of the server hosting Phabricator. Click the “Save Config Entry” button once done.

      [ { "type": "client", "host": "IP-ADDRESS", "port": 22280, "protocol": "http" }, { "type": "admin", "host": "", "port": 22281, "protocol": "http" } ]

    Here’s what the result should look like:

    Server configuration

  • Open port 22280 in the server firewall. Refer to the FAQ for more information on how to do this.

Real-time notifications should now be enabled.

Last modification June 16, 2021