Page MenuHomePhabricator

Introduce static HTML webservice type on Toolforge
Open, Needs TriagePublic

Description

Often times tools just want to display static HTML from ~/public_html/ and that's it. The best way to do that right now is to use the php56/php72 webservice types. However, when it comes to upgrades (new OS/PHP version), we require user intervention to upgrade because we don't know that the tool is just static HTML and not actually using PHP.

Having a static HTML webservice type signals to Toolforge admins that it can be safely upgraded to the new version without user intervention.

For now, "static-html" can be an alias for php72, we don't necessarily need a separate container for it.

Event Timeline

Change 561753 had a related patch set uploaded (by Legoktm; owner: Legoktm):
[operations/software/tools-webservice@master] Add static-html webservice type that is the same as PHP 7.3

https://gerrit.wikimedia.org/r/561753

For now, "static-html" can be an alias for php72, we don't necessarily need a separate container for it.

On Gerrit @bd808 said:

I think that if we are going to have this as an option it should actually be a container that is only for static html and not including the php runtime and lighttpd config for running php. That would be less load on our systems, and less likely for folks to accidentally use features that are not expected to be used.

Change 601839 had a related patch set uploaded (by Legoktm; owner: Legoktm):
[operations/docker-images/toollabs-images@master] Add html web image

https://gerrit.wikimedia.org/r/601839

Change 601839 merged by jenkins-bot:
[operations/docker-images/toollabs-images@master] Add html web image

https://gerrit.wikimedia.org/r/c/operations/docker-images/toollabs-images/ /601839

Mentioned in SAL (#wikimedia-cloud) [2020-06-29T22:48:26Z] <legoktm> built html-sssd/web image (T241817)