-
Notifications
You must be signed in to change notification settings - Fork 927
Description
Hello,
My question is regarding the captain.<hostname>
default URL - main whether this is customisable or whether it can be accessed on another port without having to have this default in place?
The use case is when using across multiple environments such as test.clientserver.com
and staging.clientserver.com
, the captain prefix prevents the use of Cloudflare as their SSL certificates are only set for a single level of wildcarding. This is fine for containers running on the system but this prevents us being able to put the captain management console behind Cloudflare access and the firewall rules.
If it were possible to set this as a custom domain (such as captain-test.clientserver.com
) this would solve the problem, equally being able to access it via a custom port could also allow for locking down behind firewall rules.
Many thanks in advance.