Some plugins require additional configurations, like for instance the database plugin. Plugins are activated by passing n to the corresponding environment variable for a given plugin in order to not skip it, e.g. With the exception of ServerLogRedirector, all plugins are skipped by default. Nwnxee plugins are configured using environment variables passed to docker run. For any questions related to running nwserver, please refer to the nwserver README. Run the image exactly the same as you would run the urothis/nwserver image. Using the tag removes the need to manually run docker pull on your machines, and enables you to roll back in a simple and sensible manner. In comparison, the latest tag will usually hit the image cache and return an outdated build, as you have to run docker pull nwnxee/unified to update the latest image in your cache. (for example: build8193.20 or build8193.35.36)ĭue to Docker's local image cache we recommend using the tag to explicitly state which nwnx build to run.Nwnxee/unified supports the following tags: Optionally, you can use Docker to run the server with pre-built NWNX binaries. export NWNX_CORE_LOG_LEVEL=7 # Default log level for core and all pluginsĮxport NWNX_LUA_LOG_LEVEL=7 # Log level for LUA, overrides default You can set the log levels like this, which governs the verbosity of log output, with 1 being the least verbose and 7 being the most verbose.You can skip a particular plugin by adding a line that looks like this before starting nwserver-linux: export NWNX_LUA_SKIP=true.At the moment you will need to search the plugin documentation to find the correct environment variables: each plugin, located in the Plugins/ folder in the source tree, has a README.md which contains some information about the plugin. You can optionally configure plugins using environment variables.Create a startup script that looks like this: #!/bin/sh.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |