thomaszbz / native-dockerfiles-typo3 Goto Github PK

• docker
• Debian
• Typo3

Add PHP 7.x environment for TYPO3 v8.x

• max_input_vars = 1500
• create file /var/www/typo3/FIRST_INSTALL
• remove composer symlink in /var/www/typo3, do composer install in /var/webadmin/typo3_src instead (delete vendor before)

• Docker allows multiline syntax by just using a backslash () at the end of a line
• using another delimiter than slach (/) avoids a lot of escaping

Intention is that developers get empowered to test if the documentation of TYPO3 core and extension renders and looks pretty.

Optional: Add support for generation of PDF files, maybe in a Dockerfile which follows up to an existing one.

TYPO3 CMS stored their packages downloaded by composer at multiple locations. Cleanup step should take all of them into account.

@helhum gives an overview which files should be deleted for a composer cleanup:

Running rm -rf vendor/ bin/ Packages/Libraries/ composer.lock; composer install will make PHPunit work again.

Plus, typo3/vendor/ is missing in this list (at least applies for TYPO3 7.4.0 prod version).

To not destroy permissions and symlinks (not in use yet), we should use e. g.

rm -rf vendor/*

Take into account that the number of files is limited when using *. If this is a problem, go for the find command.

Since we never perform a composer update we also never change composer.lock. Therefore, we could do nothing at all or perform a

rm composer.lock # there's no composer.lock in the 6.2.14-tagged version of the repo!
git checkout composer.lock # will not work for 6.2.14-tagged version of the repo!

to get the dependencies pinned by the corresponding TYPO3 CMS commit id which we have checked out. The problem is that TYPO3 CMS 6.2.14 does not contain a composer.lock in the repo and therefore composer will create one which basically means that we can't simply switch branches after creation.

Reproduce as root:

su - webadmin
No directory, logging in with HOME=/

Composer complains because of missing file permissions.

Cannot create cache directory /home/webadmin/.composer/cache/repo/https---packagist.org/, or directory is not writable. Proceeding without cache
Cannot create cache directory /home/webadmin/.composer/cache/files/, or directory is not writable. > Cannot create cache directory /home/webadmin/.composer/cache/files/, or directory is not writable. Proceeding without cache

This is not a bug (against our feature set) as everything works. We could even investigate if we actually want to make use of composer's caching infrastructure (which has sometimes seemed to be buggy in the past)

use && instead of ; for better error tracking by Docker (interrupt further execution and hopefully get status code != 0 for errors)

update composer with can be done with a:

docker exec -it typo3 /bin/bash -c 'curl -sS https://getcomposer.org/installer | php -- --install-dir=/usr/local/bin --filename=composer'

Apply git smudging concept like in moby/moby#7198 (comment) but with safe replacements (1000 is unsafe).

If you donated for a good cause you can let us know and tell us which issue you are interested in. This is not a guarantee that this issue will be closed soon but it will motivate us to continue work on this project.

You can post your donations here or send us an E-Mail.

We suggest donations to the Red Cross refugee help.

You do not have to proof us your donation. As you can't expect your issue to be closed anyways, we don't care about fraudulent activity.

speed up autoloader with

--optimize-autoloader (-o): Convert PSR-0/4 autoloading to classmap to get a faster autoloader. This is recommended especially for production, but can take a bit of time to run so it is currently not done by default.

References:

• https://getcomposer.org/doc/03-cli.md

install apt-utils to get rid of messages like

debconf: delaying package configuration, since apt-utils is not installed

which are rendered in red but are actually not errors

Add donations section for a good cause (e.g. red cross)

• install php5-xdebug
• ip should be pinned to render this feature usable
• profiler should be enabled and disabled with a command
• there should be a share for output files of xdebug's profiler

ENV DEBIAN_FRONTEND will persist and is not recommended. Better use e.g.

RUN DEBIAN_FRONTEND=noninteractive apt-get install

References:

• moby/moby#4032
• SvenDowideit/docker@c4b9e1c

TYPO3 7.5-dev complains as of latest master 8f540ffbf880691a17d6d4c3ca4f184abba84d22

PHP always_populate_raw_post_data is deprecated
always_populate_raw_post_data=0
PHP is configured to automatically populate $HTTP_RAW_POST_DATA.
Warning: Expect fatal errors in central parts of the CMS if the value is not changed to:
always_populate_raw_post_data=-1

Other tests still go green according to TYPO3's install tool

Reason: Make use of TYPO3's deprecation concept for outdated URIs.

Officially required:

AllowOverride in the Apache configuration includes "Indexes" and "FileInfo"

Speed up composer (parallel install plugin) with a

composer global require hirak/prestissimo