Editing the Robust.ini file

Setting Up a Folder for the Robust Services

Everyone is used to the binaries ending up in a bin folder. But under dotnet the binaries will be found in a folder named "~/Source/OpenSim-Sasquatch/build/Release" instead. For backwards compatibility, I copy this folder into each region folder and name it "bin". This doesn't use a lot of disk space and makes it easy to test new versions of OpenSim in only a few regions. Here’s how you copy the binaries to the Robust folder the first time:

   cd ~/Grid/Robust
   cp r ~/Source/OpenSim-Sasquatch/build/Release bin
   cd bin
   cp Robust.HG.ini.example Robust.ini

Copy the Common Files Up into the Grid Folder

I’ll show how to edit them later. While you are still in Robust/bin you can execute these commands to copy the common files to a truly common place:

   cp config-include/GridHypergrid.ini ../ ../ ..
   cp config-include/GridCommon.ini.example ../ ../ ../GridCommon.ini
   cp config-include/osslDefaultEnable.ini ../ ../ ..
   cp config-include/osslEnable.ini.example ../ ../ ../osslEnable.ini

Edit the Robust.ini File and Make These Changes

While you are still in Robust/bin, edit the Robust.ini file in place:

Change the BaseURL to somethind like “http://yourgridname.com”
The default public and private ports are fine, unless you host more than one grid on the server.
I change the PIDfile to “../Robust.exe.pid” to put it up next to the log files
Change the ConsoleHistoryFile to "../RobustConsoleHistory.txt" to get it OUT of the bin folder
In the [Hypergrid] section, uncomment HomeURI and GatekeeperURI
In the [DatabaseService] section, fill in the MySQL opensim user and password
In the [AssetService] section, change to FSAssetConnector by commenting and uncommenting
Change the fsassets to GET THEM OUT of the bin folder:
   BaseDirectory =  "../ ../ ../Data/fsassets/data" 
   SpoolDirectory = "../. ./. ./Data/fsassets/tmp"
In the [GridService] section, change MapTileDirectory to
   MapTileDirectory = "../ ../ ../Data/maptiles"
In the [GridInfoService] section, change your gridname and gridnick.
In the [Loginservice] section, I un-comment SearchURL and DestinationGuide but dunno if they work
Uncomment and change the currency to something you like. I like “NO”
In the [MapImageService] change the maptile location AGAIN
   TilesStoragePath = "../ ../ ../Data/maptiles"
In the [GridInfoService] section, un-comment and point the welcome at an HTML page used as the
   splash page on the viewer at startup. This could also be PHP that displays statistics, etc
In the [GatekeeperServie] section, un-comment ForeignAgentsAllowed

Edit the Robust.exe.config File

This file is in bin, edit it and change change the two log file names to start with “../” to get them OUT OF THE BIN FOLDER!

Running Robust.exe the First Time

You will want to run Robust in the background in a ‘screen’ but the first time, and perhaps every time you make changes to the Robust.ini file, you can run it in an SSH terminal window. The advantage of that is the display will be in color for seeing ANGRY RED ERROR MESSAGES and the SSH window may be able to scroll back farther to find those errors. So after editing the ini file, while I am still in the bin folder, the first (few) times I just run:

   mono Robust.exe

Then 'quit' out if it to edit the ini file again. Rinse and repeat. Once it is running with no errors run it in a screen:

   screen -S Robust
   mono Robust.exe
   ^A^D

Create the First User Account

Never forget to ctrl-a ctrl-d out of a screen so that it keeps running in the background. If you need to talk to the Robust Console again, you can type:

   screen -r Robust

This connects you back up to the screen running Robust in the background. This is the Robust console and it has a prompt Robust # where you can enter commands like 'quit' or 'help' or create new user accounts like I show below. You will need a default user for creating the first region.

   create user Firstname Lastname
        #You will be prompted for password, the rest of the options can be blank
   set user level 240        #any level over 200 is an admin (can use God Mode)

Next: Editing the OpenSim.ini and other files for starting your first region