Next we’ll configure some basic information about your game. These settings determine how you connect to the game. When your game opens, the MU* description, website, etc. will appear in the AresMUSH games folder.
setup_serverscript should have created the ares user for you automatically and printed the password. You should be able to scroll back if you missed it.
Log into your Server Shell with the ‘ares’ user.
Copy/paste the following commands into the shell to run them.
curl https://raw.githubusercontent.com/aresmush/aresmush/master/bin/install > install chmod +x install ./install export NVM_DIR="$HOME/.nvm" [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"
Enter your ares password when prompted.
Enter the information about your game, as explained below.
This will take several minutes. There will be a lot of spam, but eventually it will say it’s done.
./install <game code clone URL> <Web Portal clone URL>If you don’t have a GitHub fork (or don’t know what that even means) then just leave off those URLs.
These are the basic settings you’ll need to enter:
AresMUSH is stored in GitHub, a popular software version control system. Sometimes you need to interact with GitHub to retrieve Ares code updates. For this, GitHub needs to be configured with an email and a name.
Whereas the old MUSH servers you might be useful have only one port (mush.somewhere.com port 1234) Ares actually uses several. You can use any port that isn’t already in use. On a VPS server, ports greater than 1024 are typically open.
The Telnet Port is the general one that regular MU clients connect to. (default 4201)
The Websocket Port and Engine API Port are behind-the-scenes ports that the Ares Web Portal uses to communicate with the game. (default 4202 and 4203)
The Web Portal Port is where your Web Portal is running. (default 80) ‘80’ works if the Web Portal is the only website running on the server. Otherwise you’ll need to pick a custom port and access the Web Portal through a URL like http://mush.somewhere.com:8081.