Re: php.net website

From: Date: Wed, 19 Jul 2017 19:12:26 +0000
Subject: Re: php.net website
References: 1 2 3 4 5 6  Groups: php.internals 
Request: Send a blank email to internals+get-99945@lists.php.net to get a copy of this message
Am 19.07.2017 um 19:12 schrieb Mathias Grimm <mathiasgrimm@gmail.com>: > > I think it's a great idea about docker, although a separated project. > > The wiki says minimum php is 5.3 but that page is from 2013 and would be > really great to not depend on the mirrors php version, although we can > write beautiful php even in php 4 (never did prior to 4) I think the most important thing is that the PHP-website keeps a VanillaPHP-approach. Every library or framework used for a rewrite of the PHP-website will be looked upon with different eyes and will therefore seem to be "PHP-approved" to people not that deep into the website (so about 99% of PHP-developers). So the PHP-website would - even though that might not be intended - recommend frameworks or libraries over others. And we would not want that! Just my 0.02 € Cheers Andreas > > >> On 19 July 2017 at 19:50, Sara Golemon <pollita@php.net> wrote: >> >>> On Wed, Jul 19, 2017 at 1:42 PM, Niklas Keller <me@kelunik.com> wrote: >>> We should really change that and fully move to HTTPS. >>> >> I was actually just thinking how lovely it would be to re-architect >> the mirroring process to use docker images. >> >> Benefits: >> * Usual consistent/predictable deployment arguments... >> * Full control of the webserver and PHP version (and extensions) used >> on mirrors. >> * Use docker hub as the distribution channel. (https out of the box) >> * Extra level of isolation for site hosts (web-php isn't alone on its >> hosts AIUI) >> * Apparently we could even add container image signing. >> >> That's sort of an orthogonal project to rewriting the site code, but >> it's arguably a simpler task to undertake. >> >> -Sara >>

« previous php.internals (#99945) next »