This runs the same experiment as the Standalone instance, but couples with an instance of WordPress that can manage the userbase via XMLRPC.
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.
- The build process picks up the 3 configuration files and adds them to a directory within the container, so OpenSim can use them.
- 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 instance of WordPress.
- 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 initalisation finishes (give it an extra minute), run docker-compose exec wordpress wp-init to automatically setup the WordPress instance for OpenSimulator usage.
Once the docker-compose up command is reporting all instances as done, you can visit the grid info page at localhost:8080.
Log in with the administration account (admin/password), and go to either edit an existing user, or create a new one. You should have the option to specify an avatar first and last name. If you are editing a user, click to generate a new password, and the OpenSimulator plugin will pass the avatar name and password configuration to the XMLRPC RemoteAdmin endpoint. This should then create a user for you on the grid.
For more information, see the Standalone instance.
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