Misago Docker is now available for easy Misago setup and maintenance!

I am happy to announce that Misago Docker is now available, making it much easier and faster to setup Misago site!

I've timed it: it took me 24 minutes to get new Digital Ocean droplet, point domain to it, and setup Misago with https, caching, 301 redirect from www to non-www and crontab. And most of that time was spent waiting for things to get downloaded and installed by setup tool.

In addition to Misago itself, this setup provides logging, backup & restore facilities, optional integrations with Sentry, Mailgun or Mailjet, and wizards for configuration, so no settings.py editing is required.

Setup guide has been updated accordingly and show how to use Misago Docker to setup site on Digital Ocean.

This release is first step on my work to make Misago more accessible and "mainstreamy". I have plenty of ideas how to make Misago more approachable and friendly to site administrators that would like to use it for their community, and I am optimistic that some of them will land before year ends.

I've updated docs to show how to setup Misago site on Digital Ocean using Misago-Docker: misago.gitbook.io/docs/setup

You are supposed to use docker-compose because Misago requires other services in order to work.

Each of those services does other thing that Misago site requires to work:

• misagodocker_postgres_1 is database that stores your site's data
• misagodocker_redis_1 is redis database, it stores cache data
• misagodocker_nginx-proxy_1 is nginx http server, makes site available from internet
• misagodocker_nginx-lets-encrypt_1 enables https so data going to and from your site is encrypted

Yes, if you use appctl, it will also make sure those services are running.

misago-docker now includes support and documentation for overriding standard configuration of docker-compose, settings.py and urls.py.

Please refer to project's readme for details and examples: Overriding configuration

Just make sure you are using misago-docker to run production forums, dev setup doesn't care about optimization and proper data storage to make dev easier ;)

Misago Docker has been updated to use version 2 of Let's Encrypt integration. This integration uses ACMEv2 protocol to create HTTPS certificates.

Old ACMEv1 protocol will cease to be supported starting June 1, meaning your site's HTTPS certificate will not be renewed when it expires after that date.

To update, just follow the documentation.

Misago itself allows plenty of ways for deployment, and you are free to do it your way, but as an author I've had truly terrible time trying to help people who didn't use misago-docker for setup.

@softnotch please don't use this thread to ask for help. The problem you are encountering is discussed here

Steps 3 and 4 of guide apply for any provider as long as docker compose is available and domain was already configured :)