تثبيت Discourse على Windows للتطوير

[Discourse]

This tutorial has been tested on Windows 10 and 11.

To set up a development environment for Discourse on Windows, you can do it using Windows Subsystem for Linux feature.

This setup requires the WSL 2 installation. It is only available in Windows 10 builds 18917 or higher. We’ll assume that you already installed Windows Subsystem for Linux 2 (Ubuntu) on your Windows 10 system. WARNING: Install Ubuntu 18.04, and not 20.04 since some installations will fail on 20.04. For more information see June 30th, 2020 notes at the bottom of this post.

Let’s begin!

Installing Discourse

1. Initially follow the steps from the topic Beginners Guide to Install Discourse on Ubuntu for Development until the step Clone Discourse.

@techAPJ

Install Discourse Dependencies

You will need the following packages on your system:

• Git
• rbenv or asdf
• ruby-build
• Ruby (latest stable)
• Rails
• PostgreSQL
• SQLite
• Redis
• Node.js
• pnpm
• MailHog**
• ImageMagick**

** optional

Now that we have installed Discourse dependencies, let’s move on to install Discourse itself.

2. Before setting up the database you have to start PostgreSQL service & Redis server manually using following commands

   sudo service postgresql start
   redis-server --daemonize yes
   

3. Then go through all the remaining steps of the Ubuntu guide.

@techAPJ

Clone Discourse

Clone the Discourse repository in ~/discourse folder:

git clone https://github.com/discourse/discourse.git ~/discourse

~ indicates home folder, so Discourse source code will be available in your home folder.

Setup Database

Create role with the same name as your ubuntu system username:

sudo -u postgres createuser -s "$USER"

Bootstrap Discourse

Switch to your Discourse folder:

cd ~/discourse

Install the needed gems

source ~/.bashrc
bundle install

Now that you have successfully installed gems, run these commands:

bundle exec rake db:create
bundle exec rake db:migrate
RAILS_ENV=test bundle exec rake db:create db:migrate

Try running the specs:

bundle exec rake autospec

All the tests should pass.

Start rails server:

bundle exec rails server

You should now be able to connect with your Discourse app on http://localhost:3000 - try it out!

Starting with Discourse 2.5+ EmberCLI is required in development and these additional steps will be required:

In a separate terminal instance, navigate to your discourse folder (cd ~/discourse) and run:

bin/ember-cli

You should now be able to navigate to http://localhost:4200 to see your local Discourse installation.

Creating a Command to Start Discourse

Now your development environment is almost ready. The only problem is every time when you open Ubuntu on Windows you have to start the PostgreSQL service & Redis server manually. Don’t worry we can have a workaround for this by creating a custom command

cd ~

Create a new file using the command nano start-discourse and paste the content below then save and exit.

#!/bin/bash

# to start PostgreSQL
sudo service postgresql start

# to start Redis server
redis-server --daemonize yes

Now modify the CHMOD using below command

chmod +x start-discourse

And copy the file to your bin folder

sudo cp start-discourse /usr/bin/

It’s done. Now, whenever you open the Ubuntu bash just run the command below and start developing

start-discourse

---

Alternatively, if you are using Windows 10 enterprise, pro, or education edition then you can create a Linux virtual machine in hyper-v to set up the Discourse dev environment.

Notes About Windows Environment

As of June 30, 2020:

@AndreaHabib

With the introduction of Windows 10 build 2004 and WSL 2 and many of you might run into some issues since Discourse now requires WSL 2 to actually run.
For starters: If you haven’t already, you would want to update your system to Windows 2004 (19041)
Note: Don’t install using Windows Update in the system settings as you might get errors mid-installation. Also make sure you are on Windows 1903 (18362) or 1909 (18363), you can search winver for that.

• Go to: Download Windows 10
• Click the Update Now button under Windows 10 May 2020 Update to download the update assistant and let it install and finish
• If you get any errors, then download the media creation tool, run it, and create a bootable flash drive (at least 8GB flash) and use it to install Windows.

When you are done with the Windows installation, you will need to manually install WSL 2
But first, we need to make sure that 2 features are enabled:

• Virtual Machine Platform which can be enabled directly from your Windows by going to Programs and Features and then enabling Optional Features in Turn Windows features on or off
• The other is Virtualization which can be only enabled from your BIOS. However this option can vary from one motherboard to the other. eg: on AMD it’s called SVM. So please look up your specific motherboard.

Now that you have both features enabled:

• Install Ubuntu 18.04, and not 20.04 since some installations will fail on 20.04.
• Go here and update Linux Kernel: Link in replies
• Go to this link and follow the steps: Install Windows Subsystem for Linux (WSL) on Windows 10 | Microsoft Docs
• Go to powershell (run as administrator) and run: wsl --set-version Ubuntu-18.04 2 or wsl --set-version Ubuntu 2, whichever distro shows up in wsl -l -v
• Conversion takes time, a few minutes
• Run wsl -l -v to make sure that Ubuntu is running on WSL 2

Now you can run Ubuntu-18.04 or Windows Terminal with Ubuntu and start installing the dependencies and tools

Note: If you are running into an error installing one of the gems during bundle install: Make sure you are on Ubuntu-18.04 and not 20.04

However, if you already have postgreSQL 12 and running on port 5432, you might run into some issues, since the dependencies install postgreSQL 10, which might increment the port to 5433.
To fix that:

• Open your folder in a text editor (VS Code for example)
• Go to config/database.yml
• Under development and under adapter, add a new line and then add: port: 5433
• Make sure you do the same for test and profile.

If the above doesn’t work, make sure to check if PostgreSQL is running and at which port via pg_isready. Then follow the same instructions above, setting the port equal to the one the database is running on.

FOR THE LINUX KERNEL: Updating the WSL 2 Linux kernel | Microsoft Docs

@RickyC0626

A solution that does not require explicit port configuration in database.yml

Some errors during database creation and migration:

Invalid Redis connection to a specific port / connection refusal

bundle exec rake db:create

rake aborted!
Redis::CannotConnectError: Error connecting to Redis on localhost:6379 (Errno::ECONNREFUSED)
...

Caused by:
Errno::ECONNREFUSED: Connection refused - connect(2) for 127.0.0.1:6379
...

Caused by:
IO::EINPROGRESSWaitWritable: Operation now in progress - connect(2) would block
...

Tasks: TOP => db:create => db:load_config => environment
(See full trace by running task with --trace)

From this error we can see that the port Redis uses is 6379, and we can fix this by starting the Redis server via that port.

By default, redis-server --daemonize yes should work, but if not, use:

redis-server --daemonize yes --port 6379

Check status of Redis instance:

redis-cli

127.0.0.1:6379> ping
PONG

Invalid connection to psql port

bundle exec rake db:migrate

PG::ConnectionBad: could not connect to server: No such file or directory
       Is the server running locally and accepting
       connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?

From this error we can see that PostgreSQL is having trouble connecting to port 5432. Usually starting the service should work

sudo service postgresql start

If this still doesn’t work and the error persists, try checking to see which port the service is listening from, and if necessary, change the port to the one you want in postgresql.conf:

pg_isready

/var/run/postgresql:5432 - no response
or
/var/run/postgresql:5432 - accepting connections

---

The Result

Once we have done the above or executed the start-discourse command, the two instances should run on their default/specified ports. To check their status via the default Windows cmd terminal, we can run:

netstat -anop tcp

which will show something like this:

Proto    Local Address        Foreign Address        State            PID
TCP      127.0.0.1:5432       0.0.0.0:0              LISTENING        17768
TCP      127.0.0.1:6379       0.0.0.0:0              LISTENING        17768

We have now confirmed that both our postgresql and redis-server instances are running.

We can also check the status of the instances on Ubuntu or WSL, with the following commands:

lsof -i

COMMAND     PID        USER  FD  TYPE  DEVICE  SIZE/OFF  NODE  NAME
mailcatch  3244  rickyc0626  7u  IPv4   36127       0t0   TCP  localhost:1025 (LISTEN)
mailcatch  3244  rickyc0626  8u  IPv4   36128       0t0   TCP  *:socks (LISTEN)
redis-ser  3287  rickyc0626  6u  IPv6   29352       0t0   TCP  *:6379 (LISTEN)
redis-ser  3287  rickyc0626  7u  IPv6   29353       0t0   TCP  *:6379 (LISTEN)

---

sudo ss -plunt | grep postgres

tcp  LISTEN  0  128  127.0.0.1:5432  0.0.0.0:*  users:(("postgres",pid=3070,fd=7))

---

pg_lsclusters

Ver Cluster Port Status Owner    Data directory              Log file
10  main    5432 online postgres /var/lib/postgresql/10/main /var/log/postgresql/postgresql-10-main.log

---

From here, these commands should work with no major issues, without needing to modify the database.yml file:

bundle exec rake db:create
bundle exec rake db:migrate
RAILS_ENV=test bundle exec rake db:create db:migrate

Any further issues that show up can be addressed in the future.

As of July 1, 2020

@RickyC0626

A solution that does not require explicit port configuration in database.yml

Some errors during database creation and migration:

Invalid Redis connection to a specific port / connection refusal

bundle exec rake db:create

rake aborted!
Redis::CannotConnectError: Error connecting to Redis on localhost:6379 (Errno::ECONNREFUSED)
...

Caused by:
Errno::ECONNREFUSED: Connection refused - connect(2) for 127.0.0.1:6379
...

Caused by:
IO::EINPROGRESSWaitWritable: Operation now in progress - connect(2) would block
...

Tasks: TOP => db:create => db:load_config => environment
(See full trace by running task with --trace)

From this error we can see that the port Redis uses is 6379, and we can fix this by starting the Redis server via that port.

By default, redis-server --daemonize yes should work, but if not, use:

redis-server --daemonize yes --port 6379

Check status of Redis instance:

redis-cli

127.0.0.1:6379> ping
PONG

Invalid connection to psql port

bundle exec rake db:migrate

PG::ConnectionBad: could not connect to server: No such file or directory
       Is the server running locally and accepting
       connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?

From this error we can see that PostgreSQL is having trouble connecting to port 5432. Usually starting the service should work

sudo service postgresql start

If this still doesn’t work and the error persists, try checking to see which port the service is listening from, and if necessary, change the port to the one you want in postgresql.conf:

pg_isready

/var/run/postgresql:5432 - no response
or
/var/run/postgresql:5432 - accepting connections

---

The Result

Once we have done the above or executed the start-discourse command, the two instances should run on their default/specified ports. To check their status via the default Windows cmd terminal, we can run:

netstat -anop tcp

which will show something like this:

Proto    Local Address        Foreign Address        State            PID
TCP      127.0.0.1:5432       0.0.0.0:0              LISTENING        17768
TCP      127.0.0.1:6379       0.0.0.0:0              LISTENING        17768

We have now confirmed that both our postgresql and redis-server instances are running.

We can also check the status of the instances on Ubuntu or WSL, with the following commands:

lsof -i

COMMAND     PID        USER  FD  TYPE  DEVICE  SIZE/OFF  NODE  NAME
mailcatch  3244  rickyc0626  7u  IPv4   36127       0t0   TCP  localhost:1025 (LISTEN)
mailcatch  3244  rickyc0626  8u  IPv4   36128       0t0   TCP  *:socks (LISTEN)
redis-ser  3287  rickyc0626  6u  IPv6   29352       0t0   TCP  *:6379 (LISTEN)
redis-ser  3287  rickyc0626  7u  IPv6   29353       0t0   TCP  *:6379 (LISTEN)

---

sudo ss -plunt | grep postgres

tcp  LISTEN  0  128  127.0.0.1:5432  0.0.0.0:*  users:(("postgres",pid=3070,fd=7))

---

pg_lsclusters

Ver Cluster Port Status Owner    Data directory              Log file
10  main    5432 online postgres /var/lib/postgresql/10/main /var/log/postgresql/postgresql-10-main.log

---

From here, these commands should work with no major issues, without needing to modify the database.yml file:

bundle exec rake db:create
bundle exec rake db:migrate
RAILS_ENV=test bundle exec rake db:create db:migrate

Any further issues that show up can be addressed in the future.

---

Last Reviewed by @SaraDev on 2022-06-16T02:00:00Z

---

This document is version controlled - suggest changes on github.

[Arkshine]

@Arkshine

على نظام Ubuntu 22 جديد (Windows 10، WSL2) وتثبيت Discourse ناجح، تفشل جميع صور الصور في الظهور على المنفذ الافتراضي 4200.

حسنًا، وجدت حلاً.

لاحظت أن استبدال 127.0.0.1 بـ localhost سيصلح الصور.

بعد البحث قليلاً، هذا هو الأمر الذي يمكنك استخدامه لبدء Discourse:

DISCOURSE_HOSTNAME=localhost UNICORN_LISTENER=localhost:3000 bin/ember-cli -u

---

سأحاول تحديث الدليل لاحقًا.

[Arkshine]

هل هناك فرصة لمراجعة طلب السحب هذا؟

FIX: The PostgreSQL service not starting after installation (WSL2 context)

هذا من شأنه أن يجعل هذا الدليل أكثر سهولة.

[Will_S1 (Will S)]

هل لديك فكرة عن سبب حصولي على “للأسف، حدث خطأ غير متوقع، ولا يمكن لـ Bundler المتابعة.” بعد bundle install؟

[D111 (D)]

نفس المشكلة

[sam (Sam Saffron)]

هل يمكنك تقديم لقطة شاشة للخطأ؟ ما هو إصدار Ruby المثبت لديك؟

[frocm]

أواجه مشكلة في التبعيات:

ux430uq@Asus-UX430UQ:~/discourse$ bundle install
You must use Bundler 2 or greater with this lockfile.
ux430uq@Asus-UX430UQ:~/discourse$ bundler -v
Bundler version 1.16.1

ux430uq@Asus-UX430UQ:~/discourse$ gem install bundler

Fetching: bundler-2.4.20.gem (100%)
ERROR:  While executing gem ... (Gem::FilePermissionError)
    You don't have write permissions for the /var/lib/gems/2.5.0 directory.
ux430uq@Asus-UX430UQ:~/discourse$
ux430uq@Asus-UX430UQ:~/discourse$ sudo gem install bundler
[sudo] password for ux430uq:
Fetching: bundler-2.4.20.gem (100%)
ERROR:  Error installing bundler:
        The last version of bundler (>= 0) to support your Ruby & RubyGems was 2.3.26. Try installing it with `gem install bundler -v 2.3.26`
        bundler requires Ruby version >= 2.6.0. The current ruby version is 2.5.0.
ux430uq@Asus-UX430UQ:~/discourse$ bundler -v
Bundler version 1.16.1
ux430uq@Asus-UX430UQ:~/discourse$

كيف يمكنني إصلاح ذلك بسهولة؟ كنت أحاول تثبيت 2.6.0، ثم 2.7.0، ولكن كانت هناك دائمًا مشاكل أخرى مع هذا.

[AliBenBongo]

كما ورد في بعض التعليقات السابقة، واجهت أيضًا بعض الصعوبات والأخطاء أثناء محاولة اتباع هذا الدليل - جربت على كل من سطح مكتب يعمل بنظام Windows 10 و Windows 11.

بعد بعض التجربة والخطأ، توصلت أخيرًا إلى خطوات تؤدي إلى بيئة تطوير تعمل بالكامل تحت نظام Windows 11، تم اختبارها على أحدث إصدار 22H2 وأيضًا على الإصدار القادم 23H2 Release Preview (أفترض أنه سيعمل أيضًا على أحدث إصدار من Windows 10).

إذا كان ذلك مفيدًا لأي شخص، فقد نشرت الدليل للتو هنا: -

Guide to Setting Up Discourse Development Environment - Windows 11

Hi Everyone, After spending some time attempting to get a working development environment up and running under Windows 11 / WSL2 I thought I would share the steps that I have followed. This is my first post here so I hope that this is of use to somebody I am a Systems Administrator used to working with Windows so this has been an interesting journey learning Linux / Ruby / Discourse etc. A few things seem to have changed since the guide for Windows 10 was written and I ran into…

آمل أن يساعد هذا الأشخاص مثلي الذين يحاولون تشغيل Discourse تحت نظام Windows

[Canapin (Coin-coin le Canapin)]

لقد مررت بهذا الدليل الرسمي بأكمله مرة أخرى للتأكد من عدم تعطل أي شيء منذ محاولتي الأخيرة.
لقد قمت بتثبيت Ubuntu (إصدار غير محدد) عبر WSL على نظام Windows 11، والذي قام بتثبيت أحدث إصدار LTS، وهو 22.04 في هذه الحالة.

لم أواجه أي مشاكل؛ كل شيء كان مباشرًا، بدون أخطاء، وتثبيت التطوير يعمل.

إذا واجهت صعوبة في تثبيت شيء ما باستخدام أحد أدلتنا الرسمية في المستقبل، فيرجى تدوين الأخطاء والإبلاغ عنها لنا، فهذا مفيد دائمًا

---

تحذيران مع ذلك:

عند تثبيت Node.js:

================================================================================
▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
================================================================================

                           تحذير إيقاف البرنامج النصي
  هذا البرنامج النصي، الموجود على https://deb.nodesource.com/setup_X، والذي كان
  يُستخدم لتثبيت Node.js، تم إيقافه الآن وسيتم جعله غير نشط في النهاية.

  يرجى زيارة مستودع توزيعات NodeSource على Github واتباع
  التعليمات لترحيل المستودع الخاص بك.
  https://github.com/nodesource/distributions

  يحتوي مستودع GitHub لتوزيعات Node.js Linux على
  معلومات حول إصدارات Node.js وتوزيعات Linux
  المدعومة وكيفية تثبيتها.
  https://github.com/nodesource/distributions


                          تحذير إيقاف البرنامج النصي

================================================================================
▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
================================================================================

لتجنب هذا الانتظار، قم بترحيل البرنامج النصي
سيستمر في 60 ثانية (اضغط Ctrl-C للإلغاء) ...

عند تشغيل redis-server --daemonize yes:

# تحذير يجب تمكين تجاوز تخصيص الذاكرة! بدون ذلك، قد يفشل الحفظ في الخلفية أو النسخ المتماثل في ظروف الذاكرة المنخفضة. عند تعطيله، يمكن أن يتسبب أيضًا في فشل دون وجود ذاكرة منخفضة، انظر https://github.com/jemalloc/jemalloc/issues/1328. لإصلاح هذه المشكلة، أضف 'vm.overcommit_memory = 1' إلى /etc/sysctl.conf ثم أعد التشغيل أو قم بتشغيل الأمر 'sysctl vm.overcommit_memory=1' ليصبح هذا ساري المفعول.

[AliBenBongo]

لست متأكدًا من سبب وجود العديد من المشكلات لدي حينها! ربما كان هناك شيء غريب في تثبيت ويندوز الخاص بي تمكنت من إصلاحه أثناء استكشاف الأخطاء وإصلاحها دون أن أدرك ذلك!

ومع ذلك، ما زلت سعيدًا بما تعلمته حتى الآن وأتطلع إلى مواصلة العمل على ترحيل منتدياتي إلى Discourse.

[Arkshine]

@Canapin

لقد مررت بهذا الدليل الرسمي بأكمله مرة أخرى للتأكد من عدم تعطل أي شيء منذ محاولتي الأخيرة.

لقد اضطررت إلى إعادة تثبيت ويندوز، ولدي الآن ويندوز 11 جديد مثبت.
سأتبع الدليل وأبلغ لاحقًا! سأضع دليل @AliBenBongo في الاعتبار أيضًا.

[Arkshine]

هذا متابعة.
بالتأكيد يمكن الاستعانة بدليل محدّث، لكنه لا يزال يعمل بشكل رائع على نظام Windows 11 22H2 جديد.
المشكلة الوحيدة التي واجهتني، كانت أنه حتى مع عمل أمر wsl في الطرفية، فإن ميزة WSL لم تكن ممكّنة افتراضيًا:

[NateDhaliwal]

أعتقد أن هذا الدليل قديم. الخطوات المذكورة في دليل Ubuntu/Debian لم تعد موجودة.

[NateDhaliwal]

هل هناك طريقة للتراجع عن كل هذه الخطوات، على سبيل المثال، عكس البرنامج النصي للتثبيت للحزم والجواهر والاستنساخ؟

[TempAccount]

@Discourse

تحذير: قم بتثبيت Ubuntu 18.04، وليس 20.04 لأن بعض عمليات التثبيت ستفشل على 20.04.

هل لا يزال تثبيت 18.04 فوق 20.04 مطلوبًا؟

تلقي خطأ عند تثبيت nodejs:

# apt install nodejs

قراءة قوائم الحزم... تم
بناء شجرة الاعتماديات
قراءة معلومات الحالة... تم
تعذر تثبيت بعض الحزم. قد يعني هذا أنك طلبت
وضعًا مستحيلًا أو إذا كنت تستخدم التوزيعة غير المستقرة
فإن بعض الحزم المطلوبة لم يتم إنشاؤها بعد
أو تم نقلها خارج Incoming.
قد تساعد المعلومات التالية في حل الموقف:

الحزم التالية لديها اعتماديات غير ملباة:
 nodejs : يعتمد على: libc6 (>= 2.28) ولكن سيتم تثبيت 2.27-3ubuntu1.6
E: تعذر تصحيح المشاكل، لديك حزم معطلة.```