We are not changing that, I mean, all the Discourse configuration files are placed in
/opt/bitnami/apps/discourse/htdocs/config/ and with the files in place, we start the Discourse process, then the initialization is handled by Discourse itself. In that case, Discourse is already initialized so there should be a process to restart that configuration.
In the deprecated doc, it says something like
bin/bundle exec bin/rake multisite:migrate RAILS_ENV='production'
bin/rake admin:create RAILS_ENV='production' RAILS_DB=DATABASE_NAME
in the new version, there should be a similar way to reset the Discourse process taking into account the new configuration.
At bitnami level, you can do execute
sudo /opt/bitnami/ctlscript.sh restart to restart all the services associated with Discourse:
$ sudo /opt/bitnami/ctlscript.sh restart
/opt/bitnami/apache2/scripts/ctl.sh : httpd stopped
/opt/bitnami/php/scripts/ctl.sh : php-fpm stopped
/opt/bitnami/apps/discourse/scripts/sidekiq.sh : discourse_sidekiq stopped
/opt/bitnami/redis/scripts/ctl.sh : redis stopped
waiting for server to shut down.... done
/opt/bitnami/postgresql/scripts/ctl.sh : postgresql stopped
waiting for server to start.... done
/opt/bitnami/postgresql/scripts/ctl.sh : postgresql started at port 5432
/opt/bitnami/redis/scripts/ctl.sh : redis started at port 6379
/opt/bitnami/apps/discourse/scripts/sidekiq.sh : discourse_sidekiq started
/opt/bitnami/php/scripts/ctl.sh : php-fpm started
/opt/bitnami/apache2/scripts/ctl.sh : httpd started at port 80
Carlos R. Hernández