Migrate to php-fpm config from Services Flake

Created on 18 June 2025, about 2 months ago

Problem/Motivation

After a routine flake update, the environment does not build, due to a namespace conflict with services.php-fpm. This is because PHP-FPM has been added to the upstream Services Flake.

Steps to reproduce

Run nix flake update, and attempt to use nix develop.

Proposed resolution

For the short term, I have rolled back the services-flake source in the flake.lock -- if you use the flake.lock from this project now, it should continue to work.

Refactor custom php-fpm service to use the upstream from Services Flake.

Remaining tasks

User interface changes

API changes

Data model changes

πŸ“Œ Task
Status

Active

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States freelock Seattle

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @freelock
  • πŸ‡ΊπŸ‡ΈUnited States freelock Seattle

    Looking at services-flake closer, their version of php-fpm does not provide any way to select a different version of PHP -- which is one of our core needs with Drupal Flake.

    So at this point I'm going to keep our current php service, but rename it to avoid the naming collision.

    The upstream uses phpfpm, so I'm renaming our local custom service to php-fpm.

    • freelock β†’ committed 8396b4f0 on 1.0.x
      [#3530842] fix: Fix name collision of php-fpm service from Services...
  • πŸ‡ΊπŸ‡ΈUnited States freelock Seattle

    Renamed the custom phpfpm service to php-fpm, to avoid name collision with services flake.

    Keeping the custom service configuration because the upstream one for services flake does not currently support selecting the php version or adding custom modules. See https://github.com/juspay/services-flake/issues/569 .

Production build 0.71.5 2024