Skip to main content

Tuleap Community Edition development and releases are no longer public. You have until September 30th to download packages and sources in Tuleap project. You can contact the team if you need further assistance.

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #20942 Allow to run php 7.4 fpm pool
    Infos
    #20942
    Manuel Vacelet (vaceletm)
    2021-04-22 11:57
    2021-04-21 16:10
    22538
    Details
    Allow to run php 7.4 fpm pool

    As part of request #20938 it should be possible to run php74 fpm pool instead of php73

    Design proposal:

    • tuleap-php74-fpm is started in parallel of tuleap-php-fpm but listening on new ports: 9003 and 9004 (long running requests) on all platforms
    • site-deploy:nginx will modify tuleap.conf to point toward new ports when configured with --php-version=php74
    Installation process
    Empty
    Empty
    • [x] enhancement
    • [x] internal improvement
    Empty
    Stage
    Manuel Vacelet (vaceletm)
    Declined
    2021-04-22
    Attachments
    Empty
    References
    Referencing request #20942

    Artifact

    request #20938 Add support of PHP 7.4
    Referenced by request #20942

    Artifact

    request #20938 Add support of PHP 7.4
    Display settings

    Follow-ups

    User avatar
    Manuel Vacelet (vaceletm)2021-04-22 11:57

    Was actually not needed. systemd allow to locally override units with tuleap-php-fpm, that's what can be done on platforms that want to test.

    [Unit]
Conflicts=php73-php-fpm.service php74-php-fpm.service


[Service]
PIDFile=/var/opt/remi/php74/run/php-fpm/php-fpm.pid
EnvironmentFile=/etc/opt/remi/php74/sysconfig/php-fpm
ExecStart=
ExecStart=/opt/remi/php74/root/usr/sbin/php-fpm --nodaemonize
    • Status changed from Under implementation to Declined
    • Close date set to 2021-04-22
    User avatar
    Manuel Vacelet (vaceletm)2021-04-21 16:23
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes