Commit 6b51f308 changed server_https to replace entire config file contents, overwriting any earlier edits made by server_name. Although there's probably a better solution to enforce or remove dependence on order of setup functions in metabase.sh (combine server_https and server_name into one?) simply moving server_https to the first operation is an expedient fix.

This allows us to control when changes are made to the docker image
that could affect our CI system. This fork is based off the same image
we were using previously, just rolling back a change that was causing
a build failure.