Run one of the example commands in Powershell on Windows, or in bash on Linux. The commands in the examples below are bind-mounting these directories to the container and they must exist or you will get a nasty error. #Mtasa community manualRequired manual setupĬreate an empty directory somewhere on your disk, then navigate to it and create directories named: You should really consider using a Docker Compose setup as described in this section. This is just for reference and basic testing. TODO: More on that will be here soon Usage via command line It's recommended to use this image in a Docker Compose setup, because it's much easier to maintain and configure everything with a YAML file instead of passing all of the options via command line. MTA_SERVER_CONFIG_FILE_NAME - custom name of the config file, useful for switching between configs for different environments i.e.More screenshotsĭirectory structure after running the command visible in the screenshot above (before running it, it was three empty folders) If some essential config files are totally missing, then they will be added for you from the baseconfig package, But if you already have your own resources and configs then don't worry - they will NOT be overwritten. Note: The automatic resources downloader and baseconfig provider mentioned above don't interfere with your existing files. It's battle-tested: I'm using this image by myself in 4 different environments and I consider it production-ready :) If you want to use them, just remember to add proper entries to your server config. Fully prepared for running as a non-root userįor maximum compatibility with older scripts, the legacy native modules are also included in this image:.Ready for fastdl setups (hosting client files over external HTTP servers).Simple directory structure on the root level ( /) inside the image which makes them easier to find and mount. #Mtasa community full
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |