This experiment runs OpenSimulator in the most basic format - standalone mode. Best mode for getting started with OpenSimulator.
Check the repository root readme for answers to most questions.
The compose script will do the following:
- Starts up a OpenSimulator server, using an OpenSimulator Docker image.
- A health check is in place to ensure everything starts after MariaDB finishes.
- Starts up a copy of MariaDB Server 10.5.
- You can swap to MySQL if you prefer - they're largely compatible with each other.
- Be aware of a modern charset database limitation - this is why 10.5 is used.
- Starts up an NGINX web server - this is to show the grid welcome screen, and more details.
- OpenSimulator begins when the database instance reports it has finished initialising. It will create a db, populate it, then advertise that it is ready to accept connections.
Once the docker-compose up command is reporting all instances as done, you can visit the grid info page at localhost:8080.
OpenSimulator will load in our three configuration files. Left untouched, it will instruct OpenSim to operate:
- In Standalone grid mode, meaning the region, estates, users and their inventories are all stored within this one instance.
- Tells OpenSimulator we want our data stored in the counterpart MariaDB (MySQL) database.
- Create a Region at vector point 1000,1000 (what does this mean? Sheldon explains it well).
- We also tie an estate owner account to be created with this region, called Govenor Linden (play on the Linden Labs NPC).
Open started, you can point your OpenSimulator viewer to localhost:9000 and connect with credentials Governor Linden and password.
The configuration files are built into the image, so if you change the configuration files found in .docker, then you will need to run the following commands to rebuild the image (will not lose any data).
docker-compose up --build -d