Generated config missing home option about thelounge.github.io HOT 3 CLOSED

Hey @dideler! Browsing the history, I can't even find where that option was removed. I can't even tell you for sure if it has ever been a thing :D

So to answer your question, yes this option is unsupported and I have even removed it in the complete doc rewrite that I'm actively working on right now.

Regarding the desired behavior, well, that's precisely why this option would be so broken: it's a field in the configuration file to instruct The Lounge where to look for... the configuration file!
There are 2 alternatives to this at the moment: either use the --home CLI option (lounge start --home /etc/lounge/) or the $LOUNGE_HOME environment variable (LOUNGE_HOME=/etc/lounge lounge start). Happy to hear suggestions to improve this.

from thelounge.github.io.

Yeah you're right, realised that the suggested Procfile for Heroku specifies the home path:

web: node index --private --home /app

Didn't know about the LOUNGE_HOME env var, thanks.

I'll leave this issue open so it can be resolved when your docs branch is merged.

from thelounge.github.io.

Just an FYI, as of upcoming v2.5.0, --home will be deprecated in favor of the LOUNGE_HOME environment variable.
There will also be a .lounge_home file in the folder where The Lounge is installed, but while anyone can edit this, it is more intended for package installers that install in non-default locations, like https://github.com/thelounge/deb-lounge in /etc/lounge.

from thelounge.github.io.