-
-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: rename host
-> owner
#625
Comments
Well, I think |
Why not otherwise have domain accept forms such as |
Well, thats the best way of understanding. But is this technically possible? I know you are the maintainer so you don't suggest things that won't work I think. Do we need this |
In general, domains are of the form Overall I think what's needed:
So in the end, we would just have the |
Okay, got it. But why remove the documentation? Then we have an undocumentated field, that is not very nice. I would suggest to move the documentation to another plac, like archive or something like that. |
Because the code would still be functional with the older host field, and I hope we wouldn't need it going forward. Older documentation can still be accessed by accessing release tagged trees on github (or specific commits). If people already using the program can migrate to the newer format, that's also better for a smoother migration to a v3 release 😉 |
I'm still not convinced about having an undocumented field, but it's not my project, I would solve it differently. |
The current parameter
host
is a computer name in a network and is not a perfect name, despite being used by a few providers on their Web UI.subdomain
is problematic/misleading since for examplea.b.c.com
is a subdomain ofb.c.com
, despite the domain beingc.com
; plus@
or*
are not really subdomains. The technical DNS name for this left part for a certain domain isowner
, and we should use it to avoid confusion.The text was updated successfully, but these errors were encountered: