Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Apply patches after related config file is created #168

Open
Player505 opened this issue Feb 11, 2024 · 2 comments
Open

Apply patches after related config file is created #168

Player505 opened this issue Feb 11, 2024 · 2 comments

Comments

@Player505
Copy link

Related to docker-minecraft-server issue #2522
Just thought I'd make an issue here too but from what I can see it's the same as the docker-minecraft-server issue.
I'm aware I can just mount the config file but would like to minimise the number of files needed to replicate on fresh system.

docker-compose.yml

version: "3.8"

services:
  proxy:
    image: itzg/bungeecord
    tty: true
    stdin_open: true
    ports:
      - "25565:25577"
      - "19132:19132/udp"
      - "24454:24454/udp"
    volumes:
     - ./velocity.toml:/server/velocity.toml
     - ./forwarding.secret:/server/forwarding.secret
    #- ./plugins:/plugins
     - ./patch.json:/server/patch.json
    environment:
      TYPE: VELOCITY
     #ICON: ~/server-icon.png
      MEMORY: 512m
      MODRINTH_PROJECTS: viaversion, viabackwards, viarewind
      MINECRAFT_VERSION: "1.20.1"
      PATCH_DEFINITIONS: /server/patch.json
    links:
      - limbo
    restart: always

patch.json

{
 "patches": [
    {
      "file": "/server/plugins/viaversion/config.yml",
      "ops": [
        {
          "$set": {
            "path": "$.max-pps",
            "value": -1
          }
        }
      ]
    }
  ]
}
Copy link

This issue is stale because it has been open 30 days with no activity. Please add a comment describing the reason to keep this issue open.

Copy link

This issue is stale because it has been open 30 days with no activity. Please add a comment describing the reason to keep this issue open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants