amorfo77/docker-minecraft-server
1
0 Fork 0
mirror of https://github.com/itzg/docker-minecraft-server.git synced 2026-11-05 00:09:23 +00:00
Code Issues Projects Releases Wiki Activity

feat: added SKIP_SERVER_PROPERTIES

Browse Source 
#1108
This commit is contained in:
Geoff Bourne committed 2021-11-04 20:55:15 -05:00
1 parent 9de9ec2e34
commit 367f07b784
2 files changed
+9 -8
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

README.md
+5 -8
View File
@@ -796,18 +796,15 @@ The world will only be downloaded or copied if it doesn't exist already. Set `FO
## Server configuration ## Server configuration
By default the server configuration will be created and set based on the following By default, the server configuration will be created and set based on the following environment variables, but only the first time the server is started. If the `server.properties` file already exists, the values in them will not be changed.
environment variables, but only the first time the server is started. If the
`server.properties` file already exists, the values in them will not be changed.
If you would like to override the server configuration each time the container If you would like to override the server configuration each time the container starts up, you can set the `OVERRIDE_SERVER_PROPERTIES` environment variable like:
starts up, you can set the OVERRIDE_SERVER_PROPERTIES environment variable like:
docker run -d -e OVERRIDE_SERVER_PROPERTIES=true ... docker run -d -e OVERRIDE_SERVER_PROPERTIES=true ...
This will reset any manual configuration of the `server.properties` file, so if This will reset any manual configuration of the `server.properties` file, so if you want to make any persistent configuration changes you will need to make sure you have properly set the proper environment variables in your container configuration.
you want to make any persistent configuration changes you will need to make sure
you have properly set the proper environment variables in your docker run command (described below). In the opposite case, you can skip the startup script's creation of `server.properties`, by setting `SKIP_SERVER_PROPERTIES` to "true".
### Message of the Day ### Message of the Day
scripts/start-setupServerProperties
+4
View File
@@ -187,6 +187,7 @@ if [[ ${TYPE} == "CURSEFORGE" ]]; then
log "detected FTB, changing properties path to ${SERVER_PROPERTIES}" log "detected FTB, changing properties path to ${SERVER_PROPERTIES}"
fi fi
if ! isTrue "${SKIP_SERVER_PROPERTIES:-false}"; then
if [ ! -e "$SERVER_PROPERTIES" ]; then if [ ! -e "$SERVER_PROPERTIES" ]; then
log "Creating server.properties in ${SERVER_PROPERTIES}" log "Creating server.properties in ${SERVER_PROPERTIES}"
cp /tmp/server.properties "$SERVER_PROPERTIES" cp /tmp/server.properties "$SERVER_PROPERTIES"
@@ -203,6 +204,9 @@ elif [ -n "${OVERRIDE_SERVER_PROPERTIES}" ]; then
else else
log "server.properties already created, skipping" log "server.properties already created, skipping"
fi fi
else
log "Skipping setup of server.properties"
fi
if isTrue "${ENABLE_AUTOPAUSE}"; then if isTrue "${ENABLE_AUTOPAUSE}"; then
current_max_tick=$( grep 'max-tick-time' "$SERVER_PROPERTIES" | sed -r 's/( )+//g' | awk -F= '{print $2}' ) current_max_tick=$( grep 'max-tick-time' "$SERVER_PROPERTIES" | sed -r 's/( )+//g' | awk -F= '{print $2}' )