• Members 1 post
    Sept. 17, 2026, 7:04 p.m.

    Something that I don't believe has been mentioned by anyone yet, but what of a dockerless installation in a production or evaluation environment, for reason that the environment itself is fenced (LXC)? Proxmox does not guarantee support for nested containers, the current 9.x version of Proxmox that supports docker emulation is still a immature feature, and this software does not necessitate an entirely separate hypervisor and VM stack just to run docker containers

  • Sept. 17, 2026, 8:35 p.m.

    Hello @Demopans. This comes up once in a while but the answer is: it's a little hard to deploy Misago if you don't know what you are doing, and too many people who don't know what they are doing found it hard way and decided to blame me for it despite my warnings.

    Those problems don't exist with Docker deployments, but if you know what you are doing, you should be able to do custom docker-less deployment by studying the misago-docker's compose file, docker file, ./appctl script and settings.py file.

  • Members 3 posts
    Sept. 22, 2026, 7:36 p.m.

    Just FYI - for development only I can run Misago natively on Windows. (No notifications, no e-mails, maybe even no cache - but forum itself works nicely.)
    Don't ask how - Claude (AI) made it work. If anyone is interested, I can make it write down exact instructions.

  • Members 167 posts
    Sept. 23, 2026, 10:15 a.m.

    I'm still, and have been for four years, running misago under podman using this setup. This is not using docker compose, but standing up the individual containers/services. As such, though the example is for podman it should equally have application to docker, k8s, or linux containers.

    Things to note - none of the maintenance tools work the same way (see the maintennance tasks in the third post), and you need to define your own backup scheme.