Building the Staff Directory app in Docker I also explored using a different gem (like mini racer) that would correctly compile for ARM, or just using Node instead of V8, but neither was a good option for this project. I tried manually installing a different version of the V8 library and getting the bundle process to use that instead, but never quite got it working. And as you tend to do when running into questions like these, I went down a rabbit hole of potential work-arounds. However, I learned that the particular version of the V8 library used by therubyracer is not compiled for ARM and breaks the build.
The staff directory project is built in ruby on rails, and in this instance was using therubyracer gem, which embeds the V8 JS library. I installed Docker Desktop (hopefully not a bad idea) and tried to build the project, but bundle install failed. The light research I’d done suggested that Docker was more or less working now with M1 macs so I dived in thinking things would go smoothly. So my next step was to get Docker up and running. We’ve been using Docker extensively in our recent library projects over the past few years and the Staff Directory was setup to run inside a container on our local machines. It was really simple to run and it just worked, plain and simple. In the end, I stumbled on this amazing script by Moncef Belyamani. So I tried those too, and ran into more problems. Oh and also apparently RVM / rbenv are no longer cool and you should be using chruby or asdf. So I tried that – and then ran into all kinds of issues with managing Ruby versions. Some guides suggested setting up a parallel version of homebrew (ibrew) using Rosetta (which is a translation layer for running Intel-native code). I tried installing the tools normally and ran into multitudes of weirdness.
On my old laptop I’d typically use homebrew for managing packages and RVM (and previously rbenv) for ruby version management in different projects. My first step in starting with a new machine was to get my development environment setup. M1 Mac Mini ensconced beneath multitudes of cables in my home office However, upon trying to do make some updates to a recent project (by the way, we launched our new staff directory!) I ran into many stumbling blocks. Since roughly a year had passed since these new machines had been introduced I assumed the kinks would have been generally worked out and I was excited to give my speedy new M1 Mac Mini a test run at some serious work. Due to a battery issue with my work laptop (an Intel-based MacBook pro), I had an opportunity to try using a newer (ARM-based) M1 Mac to do development work.
0 kommentar(er)
