dae5a097e9
A deploy was running the same max ram for both the pod and the java app. This led to issues where the java app would use its max ram and the pod would think it was out of memory. It would kill the pod and the minecraft server with it, often not saving the last few minutes of progress. Now the deploy runs 1GiB extra ram than the java app.
43 lines
908 B
YAML
43 lines
908 B
YAML
image: hub.ducoterra.net/ducoterra/minecraft:1.16.4
|
|
port: 20101
|
|
max_cpu: 8
|
|
max_ram: 8
|
|
server_props: |
|
|
max-tick-time=60000
|
|
generator-settings=
|
|
force-gamemode=false
|
|
allow-nether=true
|
|
gamemode=0
|
|
broadcast-console-to-ops=true
|
|
enable-query=false
|
|
player-idle-timeout=0
|
|
difficulty=3
|
|
spawn-monsters=true
|
|
op-permission-level=4
|
|
pvp=true
|
|
snooper-enabled=true
|
|
level-type=default
|
|
hardcore=false
|
|
enable-command-block=false
|
|
max-players=20
|
|
network-compression-threshold=256
|
|
resource-pack-sha1=
|
|
max-world-size=29999984
|
|
server-port=25565
|
|
server-ip=
|
|
spawn-npcs=true
|
|
allow-flight=true
|
|
level-name=world
|
|
view-distance=32
|
|
resource-pack=
|
|
spawn-animals=true
|
|
white-list=true
|
|
generate-structures=true
|
|
online-mode=true
|
|
max-build-height=256
|
|
level-seed=
|
|
prevent-proxy-connections=false
|
|
use-native-transport=true
|
|
motd=This is gonna be interesting
|
|
enable-rcon=false
|