blob: dc9195787de31bdc5b86876fa9d6e35c8295b4ef (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
|
# Plugins
mt-multiserver-proxy loads all plugin files in the `plugins` directory
on startup. Any errors will be logged and do not prevent other plugins
from being loaded. Plugins **cannot** be (re)loaded at runtime, you
need to restart the proxy.
## Installing plugins
The recommended way to install plugins is cd'ing into the `plugins` directory,
downloading the source code (e.g. using `git clone`) into it
and starting the proxy without setting the `NoAutoPlugins` config option
to `true`.
The proxy will detect its own version automatically
and attempt to build the plugin against it, making this the easiest way
for end users to deal with versioning.
### Manual installation
To install a plugin manually, clone the repository, cd into it and run:
```
go build -buildmode=plugin
```
A .so file will be created. Copy or move this file into the `plugins`
directory. Restart the proxy to load the plugin.
### Automatic version management
To make dealing with version issues easier for end users
the `mt-build-plugin` tool is provided. It automatically detects
the correct proxy version and builds the plugin in the working directory
against it. The resulting .so file can then be used as explained above.
To use this, clone the plugin repository, cd into it and run:
```
mt-build-plugin
```
## Developing plugins
A plugin is simply a main package without a main function. Use the init
functions instead. Plugins can import
`github.com/HimbeerserverDE/mt-multiserver-proxy` and use the exported
symbols to control the behavior of the proxy. The API is documented
[here](https://pkg.go.dev/github.com/HimbeerserverDE/mt-multiserver-proxy).
**The plugin API may change at any time without warning.
Crucially, symbols may be renamed or deleted and fields may be deleted
from type definitions.**
## Common issues
If mt-multiserver-proxy prints an error similar to this:
```
plugin.Open: plugin was built with a different version of package github.com/HimbeerserverDE/mt-multiserver-proxy
```
it usually means that either the plugin or the proxy is out of date.
Upgrade the proxy and associated helper programs, then run
```
mt-build-plugin
```
in the plugin repository. It is also possible to manually run
```
go get github.com/HimbeerserverDE/mt-multiserver-proxy
```
and rebuild the plugin. You should compile the plugin and the proxy
on the same machine since the build environment needs to be identical.
My build environment can be found in
[build_env.md](https://github.com/HimbeerserverDE/mt-multiserver-proxy/blob/main/doc/build_env.md).
## Using plugins with development builds
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.
### Manual version management
You can build a development version by following the instructions in
[README.md](https://github.com/HimbeerserverDE/mt-multiserver-proxy/blob/main/README.md#development-builds).
If you want to use plugins with a proxy binary produced by `go build`
or `go run` (usually for contributing to the proxy), you have to temporarily
edit the go.mod file of your plugin. Find the line that says
`require github.com/HimbeerserverDE/mt-multiserver-proxy SOMEVERSION`
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.
|
