I'm trying Discourse for an internal forum. When I try something out, I spin up a new VM and install the latest Ubuntu and then try to install the software.
It seems the instructions for "easy Vagrant installation" assumed a totally different environment than I have -- I use bare Linux, not Windows or MacOS X. So I went with the "advanced installation" recommendation.
I'm pretty handy with the Linux command line, but the recommendations in the section ended up driving me off the rails (pun intended) at the point of installing RVM.
This note is suggestions for how to improve the installation instructions, rather than a demand for a better installation path (although that would be nice, too
First, the double SUDO command to try to get the rvm-installer is doesn't work, as it assumes that there already exists a vagrant user with sudo privileges. Neither of those are true when just following the instructions at that point. I ended up just doing wget to get the installer, and then separately running the rvm-installer as root -- much easier; I recommend updating the instructions to use that method. Also, creating the vagrant and rvm groups ahead of this point -- aptitude install for the listed packages doesn't actually create those.
Second, RVM tells me that "2.0.0-turbo" us an old and outdated version of Ruby, that doesn't even build correctly, yet that's what's recommended in the instructions. If this is actually the correct version, calling that out would help. And why can't I use the ruby that gets installed through aptitude instead?
Third, when looking for more instructions on this path, I found that there's a docker version, so I switched to that. I like Docker.
The default Docker with Ubuntu 14.04 LTS (literally, a month-old Linux installation) is 0.9.1. Yet, the Discourse scripts claim this isn't new enough and encourages an upgrade (that is not available pre-packaged.) Maybe suggesting Arch or Gentoo instead of Ubuntu would solve this? In the docker setup instructions, it suggest I edit the docker "bindings," but those are really known as "expose," so updating that would clarify.
Finally, you should include a mention of the "my-email-address@example.com" address that's used by default, because that should be edited before the first instance is created!