Our module uses its own Discourse recipe instead of discourse_docker and app.yml.
It handles the same essential setup. Discourse, PostgreSQL, Redis, storage, networking, and the initial administrator.
It works well for this standard deployment, though it doesn’t expose every advanced customization supported by Discourse’s launcher. And, we shouldn’t be doing it for one-click installation for such an already complicated deployment.
You are very welcome! Thank you for your kind and positive comments! It means a world to me!
You are right! This was a bug in the Discourse recipe. We weren’t correctly creating the initial administrator or configuring Discourse to use the local mail server.
This is now fixed. The installer asks for the administrator username, email, and password, creates an already activated admin account, and configures Discourse to send mail through the Virtualmin server.
To be clear, Discourse now just passes outgoing messages to the host’s mail server, which then delivers them normally. It does not create a mailbox or modify the host’s mail-server configuration.
All that said, please install the latest updates and give it a try again! I’d also really appreciate it if, in case things work for you, you’d link back to this comment in those Discourse Forums posts you created earlier.