Discourse setup assumes netcat is installed

I have to respectfully disagree, this really smells like bug material right here. Yes you’re printing a warning message which can be ignored but for someone installing discourse for the first time you want to make it as easy as possible to do, which means not having to dig into the source and finding out that you need to install netcat to make this work without errors. Any error will confuse the user/sysadmin which will make them spend time figuring out why it doesn’t work and git blame-ing the person who wrote it. :stuck_out_tongue:

This can be easily sidestepped with a simple check before you run the IP check, like so:

  1. Check if netcat is installed
  2. Continue if it is
  3. If it’s not print a warning message and give the user a yes/no option to continue without the check or to abort so they can install netcat (or even offer to apt/yum/pacman install it for them).

Another option that would work on more systems (though not all) then currently would be to use the /dev/tcp stack. More info on how to do this can be found here. This would fix it for Debian, and works under Ubuntu, I haven’t tried it on other distros.