The first site listed is the default that comes with the bitnami distribution. This file contains a single entry for each site. Which has the file ownership and group “bitnami” and the permissions 0644. '/opt/bitnami/apps/wordpress/conf/nf'īecause we want to host a WordPress farm we will replace this line with Include '/opt/bitnami/apps/nf' In the standard bitnami distribution this includes a single (in this example) WordPress site. You will see that this file is well named “bitnami- nf”. Include '/opt/bitnami/apache2/conf/bitnami/nf' This overwrites the default settings of the Apache webserver and loads the appropriate SSL modules (I am not exactly sure what is happening in this file yet.)Īt the bottom of this file we have the key line that actually loads the application websites into Apache. Bitnami do this by a line near the bottom of the file: Include '/opt/bitnami/apache2/conf/bitnami/nf' /opt/bitnami/apache2/conf/bitnami/nf To host the actual applications it is necessary to overwrite the configuration that gives us the default website. With a configuration file /opt/bitnami/apache2/conf/nf /opt/bitnami/apache2/conf/nf Optimisationīitnami optimise the number of threads and workers and timeouts for the Apache server by including a softlink whose target is set when the server is built or resized, Include '/opt/bitnami/apache2/conf/bitnami/nf' Applications

The Bitnami stack for deployment on AWS is beautifully crafted.Īpache is configured so that there is a default website. This is a work in progress and may be updated in future.

Bitnami wordpress stack ssl