Currently, Phabricator will not run in a setup where the domain used to access it does not contain a dot. This is explained with some browsers not being able to handle cookies correctly in this case.
However, after I am aware of this limitation, but know none of our users will use such a broken browser, I want to still use this dot-less domain.
Allowing to disable this check via configuration for example would be appreciated.
Can you just manage this locally then, or by forking. I don't think this is something we'd want to upstream.
Sure, we already patched it. I was just thinking this could be something useful to others as well.
If you do not want it up-stream, fine by me.
Will let @epriestley weigh in of course, I just think we're usually not super excited at adding configs 'with caveats' in them. It's not a great support experience. I can't find a specific list of browsers off hand though, so not sure who all this affects.
One issue with using dotless domains is that Chrome will not be usable at all, as it does not save cookies.
This is also why this check was originally implemented, to prevent dotless domains; see https://secure.phabricator.com/T754#7045