Installation issues

So, I’m playing around with the idea of setting up and running an AresMUSH (mostly I’m super keen on more scifi games) – realizing fully its very beta :slight_smile: – and here’s the issues I had with installation, for some feedback:

  1. I had to ‘gem install bundler’ to get bin/configure to work, as my system-wide bundler wasn’t found when rvm was used. This is entirely possibly based on my server being goofy and/or my error.

  2. Its not clear what ‘web socket port’ is (it is in the server.yml but not during installation)

  3. It prompted me for a database password but a) redis wasn’t configured with one, and b) it didn’t write it to secrets.yml. Now, since there was no password b) is fine except it still tried to AUTH even though no password was set.

  4. I get these errors when running anything:

    /home/ares/.rvm/gems/ruby-2.3.0/gems/ansi-1.4.3/lib/ansi/chart.rb:26: warning: key :concealed is duplicated and overwritten on line 29
    /home/ares/.rvm/gems/ruby-2.3.0/gems/wikidot-api-0.0.6/lib/wikidot_api.rb:6: warning: already initialized constant XMLRPC::Config::ENABLE_NIL_CREATE
    /home/ares/.rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/xmlrpc/config.rb:26: warning: previous definition of ENABLE_NIL_CREATE was here
    /home/ares/.rvm/gems/ruby-2.3.0/gems/wikidot-api-0.0.6/lib/wikidot_api.rb:7: warning: already initialized constant XMLRPC::Config::ENABLE_NIL_PARSER
    /home/ares/.rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/xmlrpc/config.rb:27: warning: previous definition of ENABLE_NIL_PARSER was here

I consider this actually going pretty darn smooth :slight_smile:

1 Like

Thanks for the feedback.

  1. I hadn’t had that problem, but I’ll add gem install bundler to the install script just to make sure it’s there.

  2. I fixed the configuration instructions to mention what those extra web ports are for.

bin/configure should prompt you for the websocket and web server ports, though. Didn’t it? I just tried it and it asked me for them.

  1. Yeah, the idea was for you to create a password. I’ll fix the wording so that’s hopefully more clear.

There was a bug in the configure script where it wasn’t writing it to the secrets file correctly. I’ll fix that. Had the password been saved to secrets properly, the bin/wipedb script would have programmed Redis with the password.

  1. Those are just warnings from some of the other libraries Ares is including. They aren’t hurting anything but I’ll see if I can clean them up.

Thanks again.

Oh it did, I just had no idea what it meant until I looked in the config file afterwards :slight_smile:

Ah! Gotcha.

1 Like