mirror of
https://github.com/itzg/docker-minecraft-server.git
synced 2024-06-07 19:40:43 +00:00
Mention PaperSpigot in README.md
This commit is contained in:
parent
ea78bdd559
commit
ada4a1fab5
@ -209,6 +209,61 @@ This works well if you want to have a common set of plugins in a separate
|
|||||||
location, but still have multiple worlds with different server requirements
|
location, but still have multiple worlds with different server requirements
|
||||||
in either persistent volumes or a downloadable archive.
|
in either persistent volumes or a downloadable archive.
|
||||||
|
|
||||||
|
## Running a PaperSpigot server
|
||||||
|
|
||||||
|
Enable PaperSpigot server mode by adding a `-e TYPE=PAPER -e VERSION=1.9.4` to your command-line.
|
||||||
|
|
||||||
|
docker run -d -v /path/on/host:/data \
|
||||||
|
-e TYPE=PAPER -e VERSION=1.9.4 \
|
||||||
|
-p 25565:25565 -e EULA=TRUE --name mc itzg/minecraft-server
|
||||||
|
|
||||||
|
__NOTE: to avoid pegging the CPU when running PaperSpigot,__ you will need to
|
||||||
|
pass `--noconsole` at the very end of the command line and not use `-it`. For example,
|
||||||
|
|
||||||
|
docker run -d -v /path/on/host:/data \
|
||||||
|
-e TYPE=PAPER -e VERSION=1.9.4 \
|
||||||
|
-p 25565:25565 -e EULA=TRUE --name mc itzg/minecraft-server --noconsole
|
||||||
|
|
||||||
|
You can install Bukkit plugins in two ways...
|
||||||
|
|
||||||
|
### Using the /data volume
|
||||||
|
|
||||||
|
This is the easiest way if you are using a persistent `/data` mount.
|
||||||
|
|
||||||
|
To do this, you will need to attach the container's `/data` directory
|
||||||
|
(see "Attaching data directory to host filesystem”).
|
||||||
|
Then, you can add plugins to the `/path/on/host/plugins` folder you chose. From the example above,
|
||||||
|
the `/path/on/host` folder contents look like:
|
||||||
|
|
||||||
|
```
|
||||||
|
/path/on/host
|
||||||
|
├── plugins
|
||||||
|
│ └── ... INSTALL PLUGINS HERE ...
|
||||||
|
├── ops.json
|
||||||
|
├── server.properties
|
||||||
|
├── whitelist.json
|
||||||
|
└── ...
|
||||||
|
```
|
||||||
|
|
||||||
|
If you add plugins while the container is running, you'll need to restart it to pick those
|
||||||
|
up:
|
||||||
|
|
||||||
|
docker stop mc
|
||||||
|
docker start mc
|
||||||
|
|
||||||
|
### Using separate mounts
|
||||||
|
|
||||||
|
This is the easiest way if you are using an ephemeral `/data` filesystem,
|
||||||
|
or downloading a world with the `WORLD` option.
|
||||||
|
|
||||||
|
There is one additional volume that can be mounted; `/plugins`.
|
||||||
|
Any files in this filesystem will be copied over to the main
|
||||||
|
`/data/plugins` filesystem before starting Minecraft.
|
||||||
|
|
||||||
|
This works well if you want to have a common set of plugins in a separate
|
||||||
|
location, but still have multiple worlds with different server requirements
|
||||||
|
in either persistent volumes or a downloadable archive.
|
||||||
|
|
||||||
## Using Docker Compose
|
## Using Docker Compose
|
||||||
|
|
||||||
Rather than type the server options below, the port mappings above, etc
|
Rather than type the server options below, the port mappings above, etc
|
||||||
|
Loading…
Reference in New Issue
Block a user