SYMFONY__ENV__SERVER_NAME appears to be load bearing

**Context**
Per the Readme, SYMFONY__ENV__SERVER_NAME functions as a means to specify a user readable 2FA name. However this variable appears to have much larger implications. If malformed, CSS and other app functionality breaks down. In the event that a user is attempting to utilize a reverse proxy to access the app, the value of the variable become critical as simply targeting IP:PORT is not possible.

**Request:**
_Short Term_
Additional documentation on the functioning of this variable in the readme, preferably with an added example or two for how to properly set it for normal and behind a reverse proxy operations.

_Long Term_
A reworking of the app to more gracefully handle calls from different sources (eg: SYMFONY__ENV__SERVER_NAME set to foo.bar.biz renders LAN usage from IP:Port functionally useless due to formatting and other aspects breaking) so that SYMFONY__ENV__SERVER_NAME is no longer mission critical for functionality.