تثبيت Discourse للتطوير باستخدام Docker

[Discourse]

التطوير باستخدام دوكر (Docker)

بما أن ديسكورس (Discourse) يعمل في دوكر (Docker)، يجب أن تكون قادرًا على تشغيل ديسكورس مباشرةً من دليل المصدر الخاص بك باستخدام حاوية تطوير ديسكورس (Discourse development container).

الإيجابيات: لا حاجة لتثبيت أي تبعيات للنظام، ولا حاجة لأي إعدادات على الإطلاق لإعداد بيئة تطوير بسرعة.

السلبيات: ستكون أبطأ قليلاً من بيئة التطوير الأصلية على أوبونتو (Ubuntu)، وأبطأ بكثير من التثبيت الأصلي على ماك أو إس (MacOS).

راجع أيضًا Developing Discourse using a Dev Container

الخطوة 1: تثبيت دوكر (Docker)

أوبونتو (Ubuntu)

curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
sudo apt-get update
sudo apt-get install -y docker-ce

19.10

sudo apt-get install docker.io
sudo usermod -a -G docker $USER
sudo reboot

ويندوز نظام ويندوز الفرعي لينكس (Windows WSL): أوبونتو (Ubuntu)

يمكنك تشغيل الأوامر المذكورة أعلاه داخل نظام ويندوز الفرعي لينكس (WSL)، ولكن يجب أن تكون جميع الملفات داخل نظام ملفات ويندوز الفرعي لينكس (WSL). على سبيل المثال، يعمل بشكل جيد إذا كان داخل ~/discourse ولكنه يفشل إذا تم وضعه داخل /mnt/c/discourse.

ماك أو إس (MacOS)

صورة دوكر (Docker) الخاصة بتطوير ديسكورس (Discourse) متاحة فقط لمعماريات x86_64. أجهزة ماك M1 قادرة على بدء تشغيل الصورة باستخدام محاكاة المعمارية، ولكن من غير المرجح أن يتم تشغيل ديسكورس بسبب نقص دعم inotify في QEMU.

بدلاً من ذلك، يجب عليك استخدام Install Discourse on macOS for development

الخيار 1: قم بتنزيل ملف .dmg مجمع من متجر دوكر (Docker store)
الخيار 2: brew install docker

الخطوة 2: بدء تشغيل الحاوية

استنسخ مستودع ديسكورس (Discourse repository) إلى جهازك المحلي.

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

(من جذر المصدر الخاص بك)

d/boot_dev --init
    # انتظر بينما:
    #   - يتم تثبيت التبعيات،
    #   - ترحيل قاعدة البيانات، و
    #   - يتم إنشاء مستخدم مسؤول (ستحتاج إلى التفاعل مع هذا)

# في طرفية واحدة:
d/rails s

# وفي طرفية منفصلة
d/ember-cli

…ثم افتح متصفحًا على http://localhost:4200 و ها أنت ذا!، يجب أن ترى ديسكورس (Discourse).

روابط رمزية للإضافات (Plugin Symlinks)

يدعم تدفق تطوير دوكر (Docker) الروابط الرمزية تحت الدليل plugins/، مع التحذير التالي:

كلما تم إنشاء رابط رمزي جديد للإضافة، يجب إعادة تشغيل حاوية دوكر (Docker container) باستخدام:

d/shutdown_dev; d/boot_dev

---

ملاحظات:

• لاختبار رسائل البريد الإلكتروني، قم بتشغيل MailHog:

  d/mailhog
  

• إذا كانت هناك مكتبات (gems) مفقودة، قم بتشغيل:

  d/bundle install
  

• إذا كانت هناك حاجة لترحيل قاعدة بيانات (db migration):

  d/rake db:migrate RAILS_ENV=development
  

• عندما تنتهي، يمكنك اختيار إيقاف تشغيل حاوية دوكر (Docker container) باستخدام:

  d/shutdown_dev
  

• يتم الاحتفاظ بالبيانات بين استدعاءات الحاوية في دليل tmp/postgres الخاص بجذر المصدر الخاص بك. إذا كنت تريد لأي سبب إعادة تعيين قاعدة البيانات الخاصة بك، قم بتشغيل:

  sudo rm -fr data
  

• إذا رأيت أخطاء مثل “permission denied while trying to connect to Docker” (تم رفض الإذن أثناء محاولة الاتصال بـ Docker)، قم بتشغيل:

  run `sudo usermod -aG docker ${USER}`
  sudo service docker restart
  

• إذا كنت ترغب في كشف المنافذ من الحاوية إلى الشبكة عالميًا (إيقاف تشغيل افتراضيًا) استخدم:

  d/boot_dev -p
  

• يأتي ملف Dockerfile من discourse/discourse_docker على GitHub، وتحديداً image/discourse_dev.

تشغيل الاختبارات

d/rake autospec

لتشغيل اختبارات إضافات محددة، يمكنك أيضًا القيام بشيء مثل هذا:

d/rake plugin:spec["discourse-follow"]

أو حتى شيء مثل هذا ليكون أكثر تحديدًا:

my-machine:~/discourse$ d/shell
discourse@discourse:/src$ RAILS_ENV=test /src/bin/rspec plugins/discourse-follow/spec/lib/updater_spec.rb:37

---

يتم التحكم في إصدار هذه الوثيقة - اقترح تغييرات على github.

[Geoffrey_Challen]

This is really easy to get set up! Thanks.

I’m surprised, however, by how slow the local installation is. Is there a way to adjust the container specs somehow? I’d expect a slowdown, but maybe not one so dramatic…

Thanks again.

[seanblue]

I’m trying to use Docker on Windows 10, and I have a question about the guide. I have Docker installed and it can run an ubuntu container (with basically nothing installed in the container). This docker guide just says to clone the repo next, but I can’t do that since the container doesn’t have git installed.

At this point, should I just follow the Ubuntu Guide and install all of the prerequisites in the container? Or should I be using the discourse_dev image referenced on Github? It seems like this guide is skipping over a lot of steps, but I’ve never used docker before so maybe I’m missing something.

[mentalstring (Paulo)]

@seanblue

This docker guide just says to clone the repo next, but I can’t do that since the container doesn’t have git installed.

I think what is tripping you is that you are trying to clone the repo within the container, but the git clone should be done on your machine. So if you already have git installed locally, you are close to get it working.

[seanblue]

I actually did that first, which is good. So I already have a copy of the repo on my local machine.

Do I automatically have access have my host file system from the docker container? I think I was partly confused by d/boot_dev --init because I didn’t know what the d/ part was (I don’t see a folder called d for example in the repo, even though I do see boot_dev).

[mentalstring (Paulo)]

The d is on the repo (scroll further down) — it is not a folder but a symlink to bin/docker. You should get it if you do the git clone.

I haven’t used this setup extensively myself, but my understanding is that you edit the source files directly in your host filesystem (that you have just checked out) and the docker containers mount that and run from it. The d/* scripts will to most of the docker setup work for you.

[seanblue]

@mentalstring

The d is on the repo (scroll further down), but it is not a folder but a symlink to bin/docker .

Thanks for that. I didn’t even think to look past the folders. I think I have enough information to make another pass at this.

[seanblue]

I’m still getting something wrong. Between this topic, here, and here, nowhere just states what docker command to run. I settled on docker run -ti -v LocalRepoPath:/src discourse/discourse_dev, which initialized a whole bunch of stuff and seemingly mounted the repo to /src. But I can’t run d/boot_dev --init for some reason. Even just running ls in the repo’s top-level directory gives me:

ls: cannot access 'adminjs': Input/output error
ls: cannot access 'd': Input/output error
ls: cannot access 'jsapp': Input/output error

Does anyone know what’s going on here?

[mentalstring (Paulo)]

You might be overcomplicating this: the tutorial on the first post already has everything you need to get started.

The d/* commands will do all the docker command magic so that you don’t have to. Once you have cloned the repo, the d/boot_dev --init and the d/unicorn commands (that you do on the host machine) should be all it takes to get http://localhost:9292 working. Those scripts will call docker to generate the container and start it for you. The d/shutdown_dev will stop it.

If you are getting those errors while browsing the repo files on the host, then something else seems amiss with your filesystem. Did you run out of disk space perhaps?

[seanblue]

sigh, I see. I thought those had to be run in docker. That said, d/boot_dev --init apparently doesn’t work on Windows in Powershell (which I guess is why this docker guide only mentions Mac and Ubuntu hosts). I tried to run the command in my linux subsystem (v1), but of course that fails at the docker step since I installed docker on Windows, not on the linux subsystem.

---

Next I tried to run it in git bash for Windows. I couldn’t run d/boot_dev --init (error “d/boot_dev: Is a directory”), but I was able to run bin/docker/boot_dev --init. This got a lot further, doing a bunch of pulls, but then it failed with

C:\Program Files\Docker\Docker\resources\bin\docker.exe: Error response from daemon: Mount denied:
The source path “PathToRepo/data/postgres;C”
doesn’t exist and is not known to Docker.

I was able to get past that (I think) by escaping the mount path, per:
Docker mounted volume adds ;C to end of windows path when translating from linux style path - Stack Overflow

After that I got this error:

C:\Program Files\Docker\Docker\resources\bin\docker.exe: Error response from daemon: OCI runtime create failed: container_linux.go:346: starting container process caused “exec: "C:/Program Files/Git/sbin/boot": stat C:/Program Files/Git/sbin/boot: no such file or directory”: unknown.

C:/Program Files/Git/sbin/boot doesn’t exist on my file system, so I guess the error’s not surprising. The only thing mentioning sbin/boot in the boot_dev file is this part of the docker command: discourse/discourse_dev:release /sbin/boot.

And that’s pretty much where I’m at right now… I don’t really know what to try at this point.

[mentalstring (Paulo)]

I’m afraid that’s how far I’m able to help you as I’m not familiar with windows.

Perhaps @rishabh is able to confirm whether this is supposed to work on windows too and update any missing steps for that (or add a note if it doesn’t).

[seanblue]

@sam Is what I’m trying to do even a remotely supported way of running Discourse for development? In the Windows development thread you mentioned trying this, but it hasn’t been going great so far. Basic (non-Discourse) Ubuntu containers technically work, but not the specific commands in this thread’s OP.

You originally mentioned this to me:

@sam

If you are feeling brave and are comfortable selecting the slow ring for insider builds I think WSL2 can work alright.

If not I would recommend traditional VM + docker for the easy path cause you will have more tooling.

Pure docker should work but leaves you with less flexibility.

So unless you have a suggestion to get me through the issues I’m having with Docker on Windows, it’s probably best for me to cut my losses and run it in an Ubuntu VM using something like Virtual Box.

[sam (Sam Saffron)]

So many of us are on the slow ring with zero issues. Games work, steam works everything works.

I do get the fear here, but it really is not a giant deal. Anyway if this is just too scary for you, I recommend a traditional VM like Hyper-V or VirtualBox. Install Docker in there and use our docker dev setup.

[seanblue]

If this wasn’t my primary (and only) computer I would join you on the slow ring, but I just can’t risk it. So I’ll go with a traditional VM with docker. Thanks again for the advice. I hope to have something up and running soon.

What would be sufficient for disk space and RAM to allocate to the VM? I was thinking maybe 16GB of disk space and 4GB of RAM, but I wanted to check first.

[sam (Sam Saffron)]

That would probably be enough, best way to find the ideal recipe is to experiment

[seanblue]

Alright, I’m close to getting this working for real. I have a local instance running using docker in an ubuntu VM. I assume that I should only run d/boot_dev --init the very first time, and after that I’d just run d/boot_dev. Is that accurate? The reason I ask is that d/unicorn works when I include --init, but doesn’t work when I omit the --init from d/boot_dev. When it fails to start I get the error

Could not find aws-partitions-1.270.0 in any of the sources.
Run bundle install to install missing gems.

But then running bundle install fails with

actionview_precompiler-0.2.2 requires ruby version >= 2.6, which is incompatible with the current version, ruby 2.5.1p57

Is there a specific version of ruby I should update to? Or is there something else going on?

---

My VM is Ubuntu 18.04 (LTS) and this time I was able to directly follow the instructions in the OP, so I’m not sure where I might have gone wrong (if something is wrong).

[sam (Sam Saffron)]

@seanblue

But then running bundle install fails with

You would not use bundle install you would use d/bundle install you want to install the bundle inside the container, the VM does not need Ruby.

[seanblue]

@sam

you want to install the bundle inside the container, the VM does not need Ruby.

Yeah, I had a feeling that was the case, just didn’t know what the right way of running it in the container was. Thanks again for the help!

[seanblue]

I pulled the latest version of the repo and as usual d/unicorn tells me “Run bundle install to install missing gems.”. However, this time when I run d/bundle install I get the following:

Fetching source index from https://rubygems.org/

Retrying fetcher due to error (2/4): Bundler::HTTPError Could not fetch specs from https://rubygems.org/

Retrying fetcher due to error (3/4): Bundler::HTTPError Could not fetch specs from https://rubygems.org/

Retrying fetcher due to error (4/4): Bundler::HTTPError Could not fetch specs from https://rubygems.org/

Could not fetch specs from https://rubygems.org/

So I can’t actually run Discourse at the moment. I have no idea if this is related to the pull (directly or indirectly) or if it’s something completely unrelated. Googling for the error hasn’t been particularly helpful, so I don’t know how to proceed.

[pfaffman (Jay Pfaffman)]

We you able to reach rubygems.org?