• 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 5 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.

  • Members 2 posts
    Oct. 15, 2026, 2:23 p.m.

    You can run Misago for testing or development on any platform where Pyhon and Postgress are available.

    So if you use a Virtual machine the easy way is choose a Linux OS with python 3.12 available.
    If not you have to install/build it on your own.

    On a debian based Version you can run
    apt install postgresql python3 python3-pip virtualenv bzip2 tar npm git

    On others just use the os specific command

    You can add a database user and a database with:
    su postgres
    psql
    create user devel with encrypted password 'xxx';
    create database misago owner=devel;
    exit
    exit

    Add a user if you need a new one with:
    adduser dummy

    change to the user and make installtion directory:
    su dummy
    cd /home/dummy/
    mkdir devel39

    If you have native python3.12:
    virtualenv devel39

    if you installed python via src build:
    virtualenv --python=/usr/local/bin/python3.12 devel39

    Now activate the virtual venv with:
    cd devel39/
    . bin/activate

    get Misago 0.39.6 Version
    git clone github.com/rafalp/Misago.git --branch 0.39.6 --single-branch

    Install Misago requierents:
    cd Misago
    pip3.12 install -r requirements.txt

    If you got an error try:
    pip3.12 install celery -U
    pip3.12 install -r requirements.txt

    change the database name,user,password etc in devproject/settings.py

    Now you are ready to go try:
    python3.12 manage.py

    If it works you can build the core database and an admin user with:
    python3.12 manage.py migrate
    python3.12 manage.py createsuperuser

    Now start Misago with:
    python3.12 manage.py runserver

  • Oct. 15, 2026, 2:33 p.m.

    Yup, but you also need Redis for cache and task queue with a celery worker with celery beat enabled

  • Members 2 posts
    Oct. 15, 2026, 5:55 p.m.

    To be clear this is no production installation nor one to test all features.
    Every acronym task front most notification will fail.
    the default cache is also slow, but local testing will be alleyway faster than any remote connection.

    you can change CELERY_BROKER_URL = "memory://" in devproject/settings.py to reduce errors but if you need async task you may do:
    apt install redis
    and set CELERY_BROKER_URL = "redis://localhost:6379/0" in devproject/settings.py

    And before you start misago with manage.py runserver
    celery -A devproject -b "redis://:localhost:6379/" worker -D
    nohup celery -A devproject -b "redis://localhost:6379/0" beat &

    for email notification and registration you will also need a mail server and adjust the config in devproject/settings.py