Sitemap

Learning Drupal CMS

4 min readJan 25, 2025

--

I recently discovered on LinkedIn that Drupal was launching a new tool: Drupal CMS. It’s a fully composable CMS with the promise of being low-code/no-code, ideal for most projects. Curious, I first decided to give it a shot and see how fast I could install it.

Welcome to the inside of my brain as I try out Drupal CMS!

Step 1: Diving in

The first thing I should do: go to new.drupal.org/drupal-cms and read the documentation.

But who am I kidding?

Let’s be honest, the first thing I want to do is download the tool and see if I can get it working as quickly as possible.

**Clicks on new.drupal.org/download...**

Ahah! Now we’re talking.

Press enter or click to view image in full size

Blah blah blah, “you’ll need php and composer to use the command below”. Simple enough. But which version of PHP and Composer… Maybe I should have read the doc.

Step 2: Docker magic

I’m far too lazy to write code after 5 p.m. on a Friday, so let’s just ask a robot to create a Dockerfile and a Docker Compose file.

Dockerfile

FROM php:8.3.16-apache

RUN apt-get update && \
apt-get install -y rsync zip unzip git libwebp-dev libpng-dev libjpeg-dev libfreetype-dev openssh-server && \
docker-php-ext-configure gd --with-webp --with-freetype --with-jpeg && \
docker-php-ext-install gd mysqli pdo_mysql && \
docker-php-ext-enable gd opcache && \
a2enmod rewrite && \
a2enmod headers && \
apt-get clean && \
rm -rf /var/lib/apt/lists/*

RUN pecl install apcu && \
docker-php-ext-enable apcu

RUN pecl install uploadprogress && \
docker-php-ext-enable uploadprogress

RUN echo 'output_buffering = 4096' > /usr/local/etc/php/conf.d/output-buffering.ini
RUN echo 'memory_limit = 512M' > /usr/local/etc/php/conf.d/memory-limit.ini

ENV COMPOSER_ALLOW_SUPERUSER=1
ENV COMPOSER_HOME=/tmp
RUN curl -sS https://getcomposer.org/installer | php -- --install-dir=/usr/local/bin --filename=composer

WORKDIR /var/www/html

RUN composer create-project drupal/cms . --no-interaction

RUN sed -i 's|DocumentRoot /var/www/html|DocumentRoot /var/www/html/web|' /etc/apache2/sites-available/000-default.conf && \
sed -i 's|<Directory /var/www/html>|<Directory /var/www/html/web>|' /etc/apache2/sites-available/000-default.conf

RUN mkdir /var/run/sshd
RUN echo 'root:password' | chpasswd
RUN echo 'PermitRootLogin yes' >> /etc/ssh/sshd_config

EXPOSE 22
EXPOSE 80

docker-compose.yml

services:
cms:
build:
context: .
dockerfile: Dockerfile
ports:
- "8080:80"
- "2222:22"
volumes:
- drupal-cms:/var/www/html
command: /bin/sh -c "chown -R www-data:www-data web/ && chown -R www-data:www-data vendor/ && service ssh start && apache2-foreground"
networks:
- drupal-network

db:
image: mariadb:11.4.4
environment:
MYSQL_ROOT_PASSWORD: drupal
MYSQL_DATABASE: drupal
MYSQL_USER: drupal
MYSQL_PASSWORD: drupal
volumes:
- drupal-db:/var/lib/mysql
container_name: drupal-db
networks:
- drupal-network
ports:
- "3306:3306"

volumes:
drupal-cms:
drupal-db:

networks:
drupal-network:
driver: bridge

It’s not very sexy, but it should do for now.

Next, we compose and go for chicken nuggets while it’s running.

docker-compose up --build -d

Now what? I’ve got chicken nuggets and a server up and running. Then I should… Honestly? I’m not sure.

Get Simon Labonne’s stories in your inbox

Join Medium for free to get updates from this writer.

Let’s see http://localhost:8080/ just for fun.

Step 3: Setting up Drupal CMS

Press enter or click to view image in full size
Screenshot of the Get started page of Drupal CMS

Wow. Pretty sweet. I guess I should use the… Let’s skip that step.

Press enter or click to view image in full size
Screenshot of Drupal CMS site naming step

Next…

Press enter or click to view image in full size
Screenshot of Drupal CMS database configuration

drupal, drupal, drupal… Very mindful, very secure…

Save and continue…

Press enter or click to view image in full size

Email: drupal@drupal.org
Password: drupal

Press enter or click to view image in full size
Screenshot of Drupal CMS site setting up

Figers crossed… At that point, I really wanted there to be a progress bar for the whole installation…

Press enter or click to view image in full size

Impressive! It worked!

Lessons learned

  1. I should have read the documentation.
  2. From start to finish, it takes about 5 chicken nuggets to install Drupal CMS.
  3. I must remember to change the security credentials.
  4. The sleek admin dashboard is a double-edged sword: it’s visually stunning, but my customers will want it on their websites come Monday morning.

What do you think? Let me know in the comments!

Don’t forget to like, comment, and subscribe!

Hit the notification bell so you don’t miss my next upload.

This article is not sponsored by anyone. Check the bio/description, there is no link.

--

--