I figured the best place for this kind of server-side stuff is a config.js file.
I don't really like adding an additional installation step.
Maybe we can take advantage of the scripts field to copy an editable config.js post-install? That way there's still a centralized place to change these settings, and the extra step becomes optional.
+1 to this functionality.
I would like to add the ability to specify a server and have it hide the server options when hitting it in the browser, so that IRC networks can lock it to their server if they want. Is this branch the direction the configuration is heading, or are there changes that need to be made first? This ticket is blocking ;)
@dinsley Off the top of my head, I think that would be simple to add (after these changes, that is).
Just make config.js.sample config.js and this able to automatically merge and it will be good.
Move DB config into config.js
Move port setting into config.js
Move client port setting into config.js
@thedjpetersen Done, though with Git aware of config.js, developers will have to avoid doing commit -a to keep from committing their configs.