Environment
- Yunohost version: 12.1.41.2
- Hardware: Cloud VPS, x86
Description
A Yunohost server was previously serving several domains that are all subdomains of the same parent. At that time, the parent was not configured on the server.
The set of domains being served took essentially the following form:
app1.example.tldapp2.example.tldportal.example.tld(default)
The first and second represent domains each assigned to some installed application, whereas the final represents a remaining domain reserved for access to the portal.
After establishing the configuration as such, working generally correctly, I decided to add support for e-mail addresses on the parent domain. Therefore, I proceeded to add configuration forexample.tld.
The domains already configured were recognized automatically as subdomains of the new domain, such that the list of all domains was then presented as the following simple hierarchy:
example.tldapp1.example.tldapp2.example.tldportal.example.tld(default)
At this point, the previous configuration for each domain had been preserved, while further configuration was included for the new domain.
Strangely, however, since the change from the three independent domains to the three domains and a shared parent, the final domain has no longer provided access to the portal. Instead, it serves a redirection to one of the applications (e.g.app1.example.tld), as though explicitly assigned this application. However, upon reviewing the actual configuration for the domain, I find that it has remained correctly as being without any assignment of an application.
Note that despite the general redirection, the webadmin remains accessible through its regular path,/yunohost/admin.
A further unexpected consequence of the change has been that the options for controlling the portal are now restricted to the parent domain, such that the options shown for the subdomains no longer include options for the portal.
It seems to be assumed that if a parent domain is configured, then that domain should be providing access to the portal, and moreover, providing access exclusively.
I have several concerns about this behavior.
First, although it should be allowed to restrict portal access to only one domain, I suggest that the choice of domain should be fully configurable, not bound by constraints that are strict, prescribed, and surprising.
Second, although it may be common that a parent domain is the one desired for access to the portal, it is not desired universally. Again, it should be through configuration that the behavior is determined. It should not be infeasible to use the parent domain only for e-mail while also using subdomain for access to the portal.
Finally, if a domain is not assigned any application, then access to the domain should not prompt a redirection to an application on a different domain, and especially not to a domain chosen arbitrarily.
It may not be possible to resolve all the design trade-offs at the moment, but I would like to understand whether I have any chance of the domains being used as I intend.