phpexpertsinc / dockerize Goto Github PK

There are lot of commercial apps out there like blesta, whmcs that need the ioncube extension.
This would be a big win if ioncube works

Need support for PostgreSQL 10.

This probably means adding a versioning variable POSTGRES_VERSION to dist/docker/lib/env.sh.

That should work.

The Problem:
PHP-FPM artificially truncates logs piped to STDOUT (what we do) to just 1,024 characters. This is a long-standing bug that probably will not be fixed in the foreseeable future.
https://bugs.php.net/bug.php?id=69031

The Solution:
Implement Maks3w's workaround.

Migrated from https://github.com/phpexpertsinc/docker-php/issues/6

Inspired by Reddit user CODESIGN2's comment.

See the original ticket for more information.

I have installed the latest version of dockerize-php and then ran docker-compose up. Unfortunately this results in the app throwing a 404.

I was able to fix this by modifying the default nginx file and setting the root directive to root /var/www/public; instead of root /var/www/web;

I'm not sure if this is specific to my app setup or if this is a mistake in the nginx configuration.

See composer require symfony/polyfill-uuid.

Nice idea! This is a great solution for getting started with a new project. It would be awesome if it were possible to easily update the components on projects whenever new functionality and bug fixes are contributed to this project.

The features I'm looking for are:

1. Minimal human interaction for setup or update
2. Easily individual components (PHP, DBMS, etc) forward or back to specific versions
3. Immediate access to binaries of components without having to setup symbolic links

The PHP Composer package manager is the main inspiration behind these features. It would be great if your project could act in much the same way, in that I could choose which components I want to install, and then upon installation, there would be a common bin folder that all binaries in the individual components are symbolically linked to.

For example, Composer stores its packages in vendor. You could store yours in platform. If I chose to install Postgres and PHP for example, I could end up with platform/postgres and platform/php folders. Since each of these components has their own binaries, your project could symbolically link all of them into platform/.bin.

Since creating an actual package manager like Composer would be a lot of work, you could maybe look into pulling this off with Git submodules instead? Then theplatform/postgres and platform/php would be submodules, and you could use Git hooks to setup the symbolic links within platform/.bin.

Since they are Git submodules, it would be trivial to roll forward and backwards to specific versions of each component as desired.

The only remaining piece of the puzzle would be how to create the appropriate Docker compose files that bring everything together into a properly configured LEPP stack.

Migrated from https://github.com/phpexpertsinc/docker-php/issues/7

Requirements:

1. It needs to be installed via a shell script, and not included in the web images by default.
2. It should autowire every site inside docker/web/sites/.
3. It should work on some sort of scheduler to auto-renew before 90 day expiry.