Posts tagged: compose

I learned to today that setting MEMORY on your minecraft server causes the JVM to egregiously allocate all of that memory. Not setting it causes slow downs and potential crashes, but setting INIT_MEMORY and MAX_MEMORY gives us the best of both worlds. It is allowed to use more, but does not gobble it all up on startup. In this economy we need to save all the memory we can! Here is a non-working snippet for a minecraft server deployment in kubernetes. containers: - name: dungeon image: itzg/minecraft-server env: - name: EULA value: "true" - name: INIT_MEMORY value: "512M" - name: MAX_MEMORY value: "3G" and in docker compose dungeon: image: itzg/minecraft-server environment: EULA: "true" INIT_MEMORY: "512M" MAX_MEMORY: "3G"

Today I learned that the docs in postiz are a bit behind, (fantastic docs btw, they are to the point, and cover almost all of what you need). The docs state that you need to include an R2 bucket to handle uploads. This issue [1] shows that more work has been done, one of which is local storage. The compose file [2] they use in the quick start has the required env variables to set this up. STORAGE_PROVIDER: "local" UPLOAD_DIRECTORY: "/uploads" NEXT_PUBLIC_UPLOAD_DIRECTORY: "/uploads" looking into my running instance I can see my images there. ⬢ [devtainer] ❯ podman exec postiz ls /uploads/2025/01/09 811747b3f703f5d9a7f10aff5103412ff0.jpeg a221db10a76f0c414171ab417379b09ec.jpeg References: [1]: https://github.com/gitroomhq/postiz-app/issues/322 [2]: https://docs.postiz.com/installation/docker-compose