A developer is struggling to install a local Discourse instance on Windows 11 for theme development. They tried Docker Desktop and WSL with Ubuntu but faced issues with container startup and Ruby version mismatches. The community suggests using the Ubuntu development guide within WSL, as the Windows guide essentially directs users to follow it. Another user recommends using the Bugs theme-component for easier theme testing on a public instance. The original poster appreciates the help and acknowledges the challenges of following installation guides, while the community reassures them that questions are welcome. resakdo22, Falco, Moin, pfaffman, Canapin}
Hello. I’m a developer that just recently discovered Discourse.
I’m having trouble getting a local instance of Discourse to work on my Windows 11 machine. This local instance will be used to model and edit a custom theme for future development.
Method 1: I tried using Docker Desktop, but the commands listed on the official Discourse guides are not working for me. The container doesn’t start.
Method 2: I tried Ubuntu in WSL but I encounter all sorts of problems, from ruby gems not correctly installing, to version problems (Discourse runs on Ruby 3.2 and for some reason the Ubuntu installer goes for 3.0.2).
Is there incompatibility with Windows 11? Am I missing something?
TLDR: I want to install a local instance of Discourse in my Windows 11 machine to modify CSS and show the theme changes to my employer. Help!
If you read both you will see that the Windows guide is basically telling you to open WSL and follow the Ubuntu guide . The Ubuntu guide has been reviewed recently by our team and attested to be working, and it tracks very closely what the developers here at Discourse use in day to day developments.
Don’t be sorry for that! Every question is welcome here (bonus point if used the search before asking though ).
We try to keep the dev install guides up-to-date, but sometimes they aren’t.
I’ve also encountered issues when installing it on Windows at times. It’s possible that you properly followed the steps but something is wrong in your configuration, or the guide needs to be checked up.