2025 Drupal upgrade

Last edit

Summary: g

Changed:

< # (as root) apt install composer
< # (as root) mkdir /etc/drup11/
< # (as me) composer create-project drupal/recommended-project /etc/drup11
< # composer require 'drupal/statistics:^1.0'
< # composer require 'drupal/simpleads:^2.0'
< # composer require 'drupal/backup_migrate:^5.1'
< #

to

> Conversation 2025-05-16
> * "Commerce" is now vastly vastly vastly bloated. Maybe switch to "Shopify"
> Composer lessons
> * composer require "drupal/blablab --no-update
> * composer update --dry-run
> * composter create-project
> Install
> * [x] (as root) apt install composer
> * [x] (as root) mkdir /etc/drup11/
> * [x] (as me) composer create-project drupal/recommended-project /etc/drup11
> * [x] composer require 'drupal/statistics:^1.0'
> * [x] composer require 'drupal/simpleads:^2.0'
> * [x] composer require 'drupal/backup_migrate:^5.1'

Resource: Dave Smyth, drupal consultant for Columbia, on Slack

Conversation 2025-05-16

"Commerce" is now vastly vastly vastly bloated. Maybe switch to "Shopify"

Composer lessons

composer require "drupal/blablab --no-update
composer update --dry-run
composter create-project

Install

[x] (as root) apt install composer
[x] (as root) mkdir /etc/drup11/
[x] (as me) composer create-project drupal/recommended-project /etc/drup11
[x] composer require 'drupal/statistics:^1.0'
[x] composer require 'drupal/simpleads:^2.0'
[x] composer require 'drupal/backup_migrate:^5.1'

To Do

However, it is highly suggested to remove the install.php file on production environments. If for some reason a DB got dropped, someone could visit the site and 'install' a new instance.