Route settings have been updated to allow access from both temp and non-temp URLs: they can be updated at a later time to remove rules that become obsolete, if necessary.
A custom .htaccess file is mounted in the running container, to allow customization of the Apache webserver.
A new secret is created, which holds the credentials to be used basic http authentication. If the secret is populated, the deploy command will trigger the execution of a command that will populate the .htpassw file with the appropriate entry.
Http basic auth configuration is configured via the .htaccess file.
Route settings have been updated to allow access from both temp and non-temp URLs: they can be updated at a later time to remove rules that become obsolete, if necessary.
A custom
.htaccessfile is mounted in the running container, to allow customization of the Apache webserver.A new secret is created, which holds the credentials to be used basic http authentication. If the secret is populated, the deploy command will trigger the execution of a command that will populate the
.htpasswfile with the appropriate entry. Http basic auth configuration is configured via the.htaccessfile.