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.
NOTE: Ensure that the Apache server is already configured to enable SSL connections.
Phabricator serves static resources using the URL configured in the phabricator.base-uri property. Set this property to reflect the new HTTPS URL by running the following command, depending on your installation type, and replacing the URL placeholder with the correct HTTPS URL:
* Approach A (Bitnami installations using system packages): $ /opt/bitnami/phabricator/bin/config set phabricator.base-uri URL * Approach B (Self-contained Bitnami installations): $ /opt/bitnami/apps/phabricator/htdocs/bin/config set phabricator.base-uri URL
If not using a CDN to serve static resources, also execute the following command, depending on your installation type:
* Approach A (Bitnami installations using system packages): $ sudo /opt/bitnami/apps/phabricator/htdocs/bin/config delete security.alternate-file-domain * Approach B (Self-contained Bitnami installations): $ /opt/bitnami/apps/phabricator/htdocs/bin/config delete security.alternate-file-domain