Klaus

Dockerized

 Fri, 09 Dec 2016 19:02:47 +0100 
Nearly all web projects are moved to #Docker containers now. The old infrastructure was mostly based on CentOS6/7 and the main reason for this step was the annoyance of legacy #PHP projects and their PHP version requirement conflicts. I don't need a cluster or swarm, so I have a single instance with #CentOS based #Project Atomic only. The dockerized projects include:
static pages with nginx
#TYPO3 7.6
#Drupal 8.2
#Piwik 2.17
#Revive Adserver 4.x
#OXID eShop 4.[9|10]
...

Here are some completely subjective "best practices":
  • I was a bit disappointed about most available images in Docker's Hub. But make use of the official mariadb, php, drupal, nginx images!
  • Use your Dockerfile and no massive entrypoint scripts.
  • Don't try to build a base images for all your projects, the projects have all too different requirements. Found it much easier to build custom images from the official PHP images directly with only what was really needed for the projects.
  • Think about mail delivery requirements. Does your application requires mail(), or can you configure a SMTP server. Use sSMTP if you need a local MTA.
  • Get your persistent volumes right and use the correct #SELinux labels.
  • A local repository makes deployment much easier.
  • Use #Jenkins to build and deploy new images.
  • Don't use --link, use Docker networks instead!
  • jwilder/nginx-proxy still has some bugs, especially with custom nginx configurations, but a wonderful tool.
  • jrcs/letsencrypt-nginx-proxy-companion and it was never easier to get certificates.
  • Think about reboots. How you want your containers to be managed? Services for systemctl work quite well so far.
  • Redirect your application logs to the right output. Log management I should take a look at again.

Should also get my private projects into containers next.
Klaus

PHP 7.1.0 Release Announcement

 Sat, 03 Dec 2016 14:46:16 +0100 
#^PHP: PHP 7.1.0 Release Announcement
The #PHP development team announces the immediate availability of PHP 7.1.0. This release is the first point release in the 7.x series.
PHP 7.1.0 comes with numerous improvements and new features such as
  * Nullable types
  * Void return type
  * Iterable pseudo-type
  * Class constant visiblity modifiers
  * Square bracket syntax for list() and the ability to specify keys in list()
  * Catching multiple exceptions types
Klaus

TYPO3 CMS 7 will require PHP 5.5

 Mon, 17 Nov 2014 10:56:46 +0100 
Somehow it is quite irritating the huge difference between which #PHP version is still used and which PHP versions are still officially supported.

#^PHP minimum requirements for TYPO3 CMS 7
The next major version of TYPO3 CMS will be called 7 and will have PHP version 5.5 as its minimum PHP version. We consider this step vitally important to our new release strategy for several reasons.
Klaus

phpdbg

 Mon, 23 Jun 2014 23:47:54 +0200 
Something to add to the cookbooks...

#^phpdbg | php debugger
phpdbg provides quick access to file contents with a listing facility, which understands what a method is ! Inspect and affect the environment after the execution of each opcode. Allow you to specify very precisely when to break execution. The power of PHP available to every command issued ! Detailed disassebmly enables precise debugging. Listing c...

#PHP #debug