Composer-docker VS HomeBrew

The same principle applies to any other images you may depend on, such as composer for dependency installation. Select the image tag that matches the major composer version you're using on your machine — composer:2 instead of composer:latest.

I've got a local version of PHP installed, but I really don't need it. Composer has an official docker container: https://hub.docker.com/_/composer/

I found on the docs of the composer image, in the Troubleshooting section, that composer should not be used that way. So I put it inside the Php image with COPY --from=composer /usr/bin/composer /usr/bin/composer and it worked. Thanks for the help u/effata!

I run most of the projects I develop on through a docker image. If it's a PHP project with composer dependencies, I use a composer image to install its dependencies, when I want to run it I use a php image. If the PHP image does not include the dependencies required for the project, I will look for an image within the project that is used, or build my own image serving the purpose. I like to make things easy to run and use, so that if I leave a project for a while I want it to be easy to get started again. If the project requires multiple things running, like a database, I setup docker-compose to make it easy to start a PHP container and database container alongside eachother that can communicate.

There is a hard coded case for this now in the project https://github.com/composer/docker/blob/master/1.10/docker-entrypoint.sh#L6

The /app directory is specified working directory, from composer image via https://github.com/composer/docker/blob/582c6f4e10b6b8fbf9bc1c5b02d6ec24694fe8d4/2.0/Dockerfile#L60.

Homebrew is a highly popular package manager on macOS and Linux systems, enabling users to easily install, update, and uninstall command-line tools and applications. Its design philosophy focuses on simplifying the software installation process on macOS, eliminating the need for manual downloads and compilations of software packages.

Homebrew - package manager for linux-based OSs.

Package Manager: Homebrew

Hopping from one distro to another with a different package manager might require some time to adapt. Using a package manager that can be installed on most distro is one way to help you get to work faster. Flatpak is one of them; other alternative are Snap, Nix or Homebrew. Flatpak is a good starter, and if you have a bunch of free time, I suggest trying Nix.

Are you using SQLite that ships with macOS, or SQLite installed from homebrew?

I had a different problem in the past with the SQLite that ships with macOS, and have been using SQLite from homebrew since.

So if it’s the one that comes with macOS that gives you this problem that you are having, try using SQLite from homebrew instead.

https://brew.sh/

Before we begin, make sure you have Homebrew installed on your Mac. Homebrew is a package manager that makes it easy to install software and dependencies. You can install Homebrew by following the instructions on their website: https://brew.sh/

I’m on MacOS and erlang.org, elixir-lang.org, and postgresql.org all suggest installation via Homebrew, which is a very popular package manager for MacOS.

I have always either installed Node from the installer provided by the Nodejs website or, via Brew in macOS. I have also used nvm in the past but did not know that there was a best practice to guide us.

A running Rails application needs a database to connect to. You may already have your database of choice installed, but if not, I recommend PostgreSQL, or Postgres for short. On a Mac, probably the easiest way to install it is with Posrgres.app. Another option, the one I prefer, is to use Homebrew. With Homebrew installed, this command will install PostgreSQL version 16 along with libpq:

On a macOS machine, you can use homebrew by running the command.