A dev compose file with the password misago, a plugin system listed as future work and already in the image
Misago is fully featured modern forum application that is fast, scalable and responsive.
At a glance
- What is it?
- Misago is a Django and React forum application with a large self-declared feature set and a documented development setup built entirely around Docker; the interesting material is where the documentation and the repository disagree, from a coveralls badge pointing at a branch that is not the default to a plugin directory the roadmap still lists as unwritten.
- Who is it for?
- Misago fits a team that wants a self-hosted forum with moderation queues, OAuth sign-in and a Django and React stack it can extend, and the development path is genuinely short once Docker is installed. Four things to check before you build on it.
- Can I use it commercially?
- Yes, with conditions. GPL-2.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly Python, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- rafalp/Misago2,780 ★ · -2
| Repository | 2026-10-04 | 2026-11-15 |
|---|---|---|
| rafalp/Misago | 2.8k | 2.8k |
-2 Stars in the last 42 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The development compose file ships misago and password as credentials
Both the compose file and the Dockerfile open by saying they are for local development of Misago itself and not for running a site in Docker, and the Dockerfile points at misago-docker for that. What the compose file then does is write credentials into plain text:
environment:
- POSTGRES_HOST=postgres
- POSTGRES_DB=misago
- POSTGRES_USER=misago
- POSTGRES_PASSWORD=misago
- POSTGRES_TEST_DB=misago_test
- SUPERUSER_USERNAME=Admin
- [email protected]
- SUPERUSER_PASSWORD=passwordThe database user and its password are both the word misago, and the seeded administrator is Admin with the password password, which is also what the README tells you to type at the admin panel address.
The port exposure is uneven. Postgres publishes on 127.0.0.1 only, while the application publishes ${MISAGO_DEVSERVER_PORT:-8000}:8000, which binds every interface by default, so the forum is reachable from the network on a port that can be changed by one environment variable. Redis runs with no password and no published port, and the whole project directory is mounted into the container at /app.
The compose command drops the --noreload the image sets
The image's own command is:
CMD ["python", "manage.py", "runserver", "0.0.0.0:8000", "--noreload"]and the compose service overrides it with a command that has no such flag:
command: python manage.py runserver 0.0.0.0:8000So the flag is present in the repository and absent in the documented way to run it. That is not an accident of style, because autoreload only makes sense alongside the volume mount that maps the entire project into the container, which the same file declares as .:/app:Z with a comment explaining that it keeps files in the container updated on the fly as the work happens locally. Run the image on its own and the code will not reload; run it through the compose file and it will.
The worker beside it runs celery -A devproject worker --loglevel=info, naming the development project module and setting only the log level, with no queue, concurrency or broker settings in the visible configuration. Postgres is version 15 and Redis is version 6, both pinned, and mailpit is the fourth service for catching outbound mail locally.
install_requires is the compiled lock file with its comment lines
setup.py does not list dependencies. It reads the compiled requirements file and passes its text straight through:
with open(os.path.join(SETUP_DIR, "requirements.txt"), "r") as f:
REQUIREMENTS = f.read()and then:
install_requires=REQUIREMENTS,So install_requires is the pip-compile output verbatim, including its header. That file starts by recording how it was made:
# This file is autogenerated by pip-compile with Python 3.12
# by the following command:
#
# pip-compile --output-file=requirements.txt requirements.inand every entry carries a comment naming what pulled it in, which is how a reader can tell a direct requirement from a transitive one. The visible direct entries include ariadne, ariadne-django, celery[redis], coveralls, django, djangorestframework, freezegun and html5lib.
Two pins in that list deserve a second look. defusedxml is pinned to 0.8.0rc2, a release candidate, in a file that goes into a production install path. And cryptography sits at 42.0.2 while certifi is dated 2024.2.2, next to django 5.2.15, so the cryptographic pieces are held back while the framework moves. The version itself comes from the package rather than this file, through from misago import __version__ as version.
GraphQL is pinned in the lock file and listed as future work
The feature list describes the current API as a JSON API, and the roadmap section lists replacing it:
> Replacing current API with GraphQL API for easier integrations and extending.
The dependency file disagrees with that framing. ariadne, ariadne-django and graphql-core are all pinned, and ariadne and ariadne-django both appear as direct requirements rather than as things something else dragged in. A GraphQL schema library and a Django integration for it are therefore installed by default, while the README describes the API surface as JSON.
The rest of that roadmap section lists forum-wide JavaScript routing to cut navigation time, a plugin system to extend the core package, a WYSIWYM content editor, and a ranking system for search results based on post links, likes, author and thread importance. None of those is dated, and none has a version attached to it, so the file reads as a wish list rather than a plan.
What the project does commit to is scale of feature rather than delivery dates: OAuth sign-in through Facebook, Google, Github, Steam, Blizzard.net or any other of over 50 supported providers, categories with unlimited depth, a permission system driven by rank, roles or category, a moderation queue for both users and categories, private threads, a best-answer marker, an edits log with a revert function, attachment thumbnailing with animation removal from gifs, and settings aimed at GDPR compliance.
The plugin system is future work and already runs during the image build
One line of the roadmap says a plugin system will extend the core package with new features. Three places in the repository already assume plugins exist.
There is a plugins directory at the root. The Dockerfile sets an environment variable pointing at it:
ENV MISAGO_PLUGINS "/app/plugins"and then runs a bootstrap step as part of building the image:
RUN ./dev bootstrap_pluginsBoth the Dockerfile and the compose file copy that directory into place, and the Dockerfile copies the dev script itself for the same reason.
So the mechanism is present enough to be bootstrapped on every image build, and the documentation still describes it as something to come. That is the kind of gap worth resolving in one direction or the other, because a reader deciding whether they can extend Misago with a plugin gets two different answers from the same repository.
The rest of the build follows the same pattern of development-only tooling inside the image: pip install pip-tools after installing the already-compiled requirements, apt-get with --allow-unauthenticated, and a package list that includes vim, sqlite3, locales, cron, gettext and postgresql-client-15.
A badge points at master while the default branch is main
The coverage badge in the README is built for a branch that is not the default one:
[](https://coveralls.io/github/rafalp/Misago?branch=master)The default branch of the repository is main. A badge like that renders against a branch name, so whatever it reports is either stale or reading a branch that is no longer where work lands.
The maturity signals have the same flavour. The development status line in the README points at the perpetual beta category, while the classifier in setup.py says Development Status :: 4 - Beta. The classifier list also names exactly one Python version, 3.12, which matches the interpreter the lock file was compiled with.
The release numbers tell their own story: 0.39.4 on 2025-08-09, then nothing for about nine months, then 0.39.5 on 2026-05-29 and 0.39.6 on 2026-06-19. The branch itself was pushed on 2026-09-23, so the last published release is a few months behind the tip. Nothing in the documentation says which branch a deployment should track.
Webpack, less and bootstrap, and no test suite for the frontend JavaScript
The frontend section is explicit about the risk. Apart from the Admin Panel, the interface is React.js components backed by the Django API, built with webpack, and the package tasks are:
* `npm run build`: production build of the assets, bundling and minifying JavaScript, CSS and images, moving them to the `misago/static/misago` directory. * `npm run start`: a quick build that bundles, compiles less and deploys to `misago/static/misago` without minifying, rebuilding when a less or js file changes. * `npm run prettier` and `npm run eslint`.
Two things stand out. The theme is described as custom and developed with bootstrap, while the quick build compiles less, so two styling tools are in play for one interface. And the warning about the source JavaScript is blunt: special care should be taken when changing source JavaScript files as no test suite for those exists.
The escape hatch for site owners is a template named scripts.html, which allows custom HTML and JavaScript to run before the application starts. The Admin Panel is built separately: its assets live in a misago-admin directory, deploy to misago/static/misago/admin, and have their own npm install followed by npm run build or npm run dev.
One script or four commands, and the superuser is created two ways
The short path is a single command. Clone the repository and run:
./dev initThat builds the necessary containers, installs the Python dependencies and initializes the database. After it finishes, docker compose up starts the development server, the forum is at http://127.0.0.1:8000/ and the admin panel is at http://127.0.0.1:8000/admincp/. The dev script has other actions, and running it with no arguments lists them.
The manual path is four steps and skips the script entirely:
1. `docker compose build`: builds docker containers 2. `docker compose run --rm misago python manage.py migrate`: runs migrations 3. `docker compose run --rm misago python manage.py createsuperuser`: creates admin user 4. `docker compose up`: starts dev server
The divergence is in step three. The manual path asks Django to create a superuser interactively, while the compose file pre-seeds SUPERUSER_USERNAME, SUPERUSER_EMAIL and SUPERUSER_PASSWORD, so the account the manual path creates and the account the seeded configuration creates are not the same one. Anyone following both routes in sequence ends up with two administrators and no documentation of which one the admin panel expects.
Editorial conclusion
Misago fits a team that wants a self-hosted forum with moderation queues, OAuth sign-in and a Django and React stack it can extend, and the development path is genuinely short once Docker is installed. Four things to check before you build on it. The repository ships no production Docker setup by design, and the development one seeds a database password and a superuser password in plain text. setup.py hands the whole pip-compile output file to install_requires, comment lines included, so the pinned set and the install requirements are the same artifact. GraphQL libraries are already pinned while the roadmap still describes a GraphQL API as work to come. And the plugin mechanism exists in the tree, in an environment variable and in an image build step, while the README lists a plugin system under future releases. The newest release is 0.39.6 from 2026-06-19 and the branch was pushed on 2026-09-23.
Frequently asked questions
What is Misago, and what is it built on?
A forum application written in Python and ES6, powered by Django and React.js, released under GPLv2. The interface is React.js components backed by the Django API except for the Admin Panel, assets are built with webpack, and the pinned dependency set includes django 5.2.15, djangorestframework, celery[redis] and ariadne.
How do I start a Misago development instance?
Clone the repository and run ./dev init, which builds the containers, installs the Python dependencies and initializes the database, then start it with docker compose up and open http://127.0.0.1:8000/. The Admin Panel is at http://127.0.0.1:8000/admincp/, with the username Admin and the password password.
Can this repository's Docker setup run Misago in production?
No. The compose file and the Dockerfile both state that they are only for local development of Misago itself, and the Dockerfile points at misago-docker for a production setup. What the development compose file does provide is a Postgres user and password of misago and a seeded superuser named Admin with the password password.
Which social logins and spam controls does Misago offer?
Sign in with Facebook, Google, Github, Steam, Blizzard.net or any other of over 50 supported OAuth providers. Administrators can require email activation through a link or limit activation to an administrator action, and can use a custom Q&A challenge, ReCAPTCHA, Stop Forum Spam or an IP blacklist against spam registrations.
Can Misago be connected to an existing site?
Yes, through the built-in OAuth2 client and a JSON API. The roadmap section lists replacing that API with a GraphQL API, forum-wide JavaScript routing, a plugin system, a WYSIWYM editor and a ranking system for search results as work still to come, although GraphQL libraries are already present in the pinned requirements.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/rafalp-misago)Star history chart for your README
[](https://hysenlabs.com/projects/rafalp-misago)Was this useful?