Format and spacing

This commit is contained in:
Adrián Parilli 2020-11-18 21:43:20 -04:00
parent 9230e77221
commit 8208debc1c
2 changed files with 22 additions and 6 deletions

11
Database.md Normal file
View File

@ -0,0 +1,11 @@
### Database Server
Connecting the simulator to a databse does not differ much from standard setup specified at [OpenSim Database Settings](http://opensimulator.org/wiki/Database_Settings), excepting by the fact Opensim Engine and DB Server will always reside on different hosts, and will communicate via network. You need to setup both OpenSim config files (a.k.a. DB client) and your DB Server considering this fact.
In many scenarios, you will want (or at least results practical) to run this DB Server inside a container as well. If this is the case, additional Docker setup is needed to ensure a virtual network where both containers can communicate is essential.
Finally, as an up and running DB Server is a pre-requisite for OpenSim to start, it is ideal to create a Stack with Docker Compose or Kubernetes, where the DB takes precedence starting.
Opensim Engine has been tested and runs nice with the [*Official MySQL Docker Images*](https://hub.docker.com/_/mysql) BUT,
*As of OpenSim 0.9.1.1 and based distros, 'latest' MySQL images won't work because have authentication issues, so it is recommended to use 5.7.xx images instead, until OpenSim code is updated for MySQL version 8.*

View File

@ -1,25 +1,30 @@
# OpenSim Engine -- Readme # OpenSim Engine -- Readme
## Overwiew: ## Overwiew:
OpenSim Engine is intended to run OpenSim based simulators OpenSim Engine is intended to run OpenSim based simulators. Its main goal is to be part of a more elaborated solution to deploy simulators and/or grids, but can be used *as is* to test and even run (very simple) configurations inside containers.
Although its main goal is to be part of a more elaborated solution to deploy simulators and/or grids, it can be used *as is* to test and even run (very simple) configurations inside containers.
## Features: ## Features:
- Built upon the latest version of Mono (6.xx) - Built upon the latest version of Mono
- Contains minimal tools to download and manipulate ZIP compressed binaries inside the container - Contains minimal tools to download and manipulate ZIP compressed binaries inside the container
- It runs OpenSim.exe onto a detachable console you can access the main screen, see status and use CLI. - It runs OpenSim.exe onto a detachable console you can access the main screen, see status and use CLI.
- Allows both standalone sims/grids (e.g. OpenSim, DivaDistro), and also connect your sims to existing grids (e.g. OSGrid) - Allows both standalone sims/grids (e.g. OpenSim, DivaDistro), and also connect your sims to existing grids (e.g. OSGrid)
NOTE: The image does not provide the simulator files, you have to provide them yourself. NOTE: The image does not provide simulator files, you have to download/uncompress it yourself.
## Requirements: ## Requirements:
- Docker Engine. See [Docker Documentation](https://docs.docker.com/get-docker/) for further instructions - Docker Engine. See [Docker Documentation](https://docs.docker.com/get-docker/) for further instructions
- Main simulator folder tree uncompressed, and accessible by Docker with write permissions - Uncompressed main simulator folder tree, accessible by Docker with write permissions
### Basic Usage ### Basic Usage
Useful for tests, and also for running very simple configurations (e.g. standalone and/or default SQLite setup): Useful for tests, and also for running very simple configurations (e.g. standalone and/or default SQLite setup):
`docker run -it --restart=<restart-policy> --name <container-name> -v </path-to-main-folder>:/opensim -p 9XXX[-9YYY]:9XXX[-9YYY]/tcp -p 9XXX[-9YYY]:9XXX[-9YYY]/udp adrianparilli/opensim-engine[:<label>]` `docker run \
-it --restart=<restart-policy> \
--name <container-name> \
-v </path-to-main-folder>:/opensim \
-p 9XXX[-9YYY]:9XXX[-9YYY]/tcp \
-p 9XXX[-9YYY]:9XXX[-9YYY]/udp \
adrianparilli/opensim-engine[:<label>]`
Where: Where:
`<restart-policy>`: `no` `on-failure[max-retries]` `unless-stopped` or `always` (see [Restart Policies](https://docs.docker.com/engine/reference/commandline/run/#restart-policies---restart) for more info `<restart-policy>`: `no` `on-failure[max-retries]` `unless-stopped` or `always` (see [Restart Policies](https://docs.docker.com/engine/reference/commandline/run/#restart-policies---restart) for more info