Document deployment process

Question

Document deployment process

Opened this issue 2 years ago · 3 comments

Following the merge of #408 and #604, we could switch from PSR-4 autoloader implementation taken from php-fig/fig-standards to using composer autoloading.

In order to do so, we would need to run

composer install --no-dev --optimize-autoloader

or - given that we currently do not have any production dependencies - at least

composer dump-autoload --optimize

Is there a chance we can document the deployment steps, or modify them in any way?

Answer 1 · 2022-07-11T11:56:47.000Z

I don't know exactly how the deployment works; I think it's rsync based, and the exact scripts are likely only available on the Web servers. While we should be able to get someone who could adjust the scripts, it might be hard in practise. As such, maybe leave it as is for now.

Answer 2 · 2023-06-02T12:52:33.000Z

@cmb69

As a follow up to #408, are we still using PHP 7.3 on the production system or is there a chance that we are using a PHP version that is less unsupported?

Answer 3 · 2023-11-29T15:11:19.000Z

As per @derickr, these are the current deployment steps for php.net:

People commit to https://github.com/php/web-php
Every 10 minutes (except for 23:*), the rsync.php.net (sc2.php.net server updates its knowledge of all website repositories, fetches manual notes, prepares a "mirror package", and fetch documentation
Every two hours, the rsync.php.net (sc2.php.net server) builds the documentation and its translations
Every 5 minutes, php-web4.php.net syncs it's repository from rsync.php.net, which is then exposed through Myracloud to serve www.php.net

The scripts are at https://github.com/php/systems, specifically https://github.com/php/systems/blob/master/update-everything.