diff options
| author | HimbeerserverDE <himbeerserverde@gmail.com> | 2023-12-02 19:37:31 +0100 |
|---|---|---|
| committer | HimbeerserverDE <himbeerserverde@gmail.com> | 2023-12-02 19:37:31 +0100 |
| commit | 4c5294210a19e79d759b8f0ed7dcef9aafa4059f (patch) | |
| tree | e0f069f75a505f1844b59741f8338f5b75a79b0c /doc/plugins.md | |
| parent | e180db41f514e3d769f3fa4af436d6a580487c2b (diff) | |
make auto plugin building work in dev builds
Diffstat (limited to 'doc/plugins.md')
| -rw-r--r-- | doc/plugins.md | 11 |
1 files changed, 6 insertions, 5 deletions
diff --git a/doc/plugins.md b/doc/plugins.md index d943ea0..2e9b2d2 100644 --- a/doc/plugins.md +++ b/doc/plugins.md @@ -38,8 +38,6 @@ To use this, clone the plugin repository, cd into it and run: mt-build-plugin ``` -This tool won't work in development builds. - ## Developing plugins A plugin is simply a main package without a main function. Use the init functions instead. Plugins can import @@ -84,6 +82,9 @@ and copy everything excluding the `require `. Then append a new line: `replace github.com/HimbeerserverDE/mt-multiserver-proxy SOMEVERSION => ../path/to/proxy/repo/`. Now rebuild and install the plugin and it should be loaded. -As of now there is no way to automate this, though the go toolchain -provides everything needed to implement it. -Expect this feature to be added soon. +### Automatic development version management +The `mt-build-plugin` tool as well as the proxy itself are capable of +handling development versions, but the former only works if it's located +in the same directory as the proxy executable. See +[Automatic version management](https://github.com/HimbeerserverDE/mt-multiserver-proxy/blob/main/doc/plugins.md#automatic-version-management) +for details. |