Apple M1 for discourse development

[Ahmed_Gagan]

Hi there,
I am planning to get Apple macbook pro M1 for discourse development and wanted to get some community dev’s review about Apple’s m1 processor with discourse development.

Do you suggest getting Apple MacBook pro M1 as primary discourse development device?

[sam (Sam Saffron)]

We have quite a few engineers who use an M1 for development and love it. @david can probably elaborate.

[david (David Taylor)]

Yeah it works great! Combatibility was a little rough to start with, but now Postgres/Redis/Ruby/Discourse are all working great! A huge perf upgrade compared to my previous intel MacBook. There are a few more details in this topic

[Ahmed_Gagan]

This sounds convincing thanks a lot @sam and @david I’ll post my experience when I get it delivered

[rudzainy (Rudzainy Rahman)]

Hello Anyone has Discourse development setup on an M1 machine while also developing other projects using other technologies? How’s the experience and what’s your process like?

I am developing and maintaining a few other projects and it’s been a pain to switch between them, now even more than ever because of the M1 ARM architecture. Adding and hacking configs to make things run (like different binary locations for different tech stacks and CLIs, different SSH keys for different emails) has been a real chore. So I am trying to optimise the process and am using aliases and basic scripting in my .zshrc file.

At this point in time, I just limit myself to developing my Discourse theme and reading the Discourse codebase

Reference:
Other tech stacks I’m developing on my M1 machine besides Discourse:

• Rails 6
• Rails 5 + React
• React Native

[sam (Sam Saffron)]

You can always just use our Docker setup if you want complete isolation.

It is not as fast as running native, but perfectly usable from what I hear.

Beginners Guide to Install Discourse for Development using Docker

Developing using Docker Since Discourse runs in Docker, you should be able to run Discourse directly from your source directory using a Discourse development container. Pros: No need to install any system dependencies, no configuration needed at all for setting up a development environment quickly. Cons: Will be slightly slower than the native dev environment on Ubuntu, and much slower than a native install on MacOS. Step 1: Install Docker Ubuntu curl -fsSL https://d…

[david (David Taylor)]

Unfortunately the M1 Docker implementation has some issues which mean our base image doesn’t work

Beginners Guide to Install Discourse for Development using Docker

I tried this today, and also ran into issues. The error I saw was because Docker’s architecture emulation doesn’t support inotify (which we use a lot in Discourse development). For now, I’ve added a warning to d/boot_dev when a non-x86_64 architecture is detected: ❯ d/boot_dev WARNING: Docker architecture is not x86_64. Discourse development is unlikely to work using Docker's architecture emulation. Please try a native development installation. I’ve now added a d/ember-cli helper, and forwa…

As for isolating dev environments - I guess my advice would be to make sure you’re using Bundler / Yarn to allow installing different dependencies for each project. For Ruby, there are also tools like rvm which allow you to instantly switch between different versions of Ruby.