tanoconsulting / euts Goto Github PK

It is currently possible to set up as test bench eZPublish5 on PostgreSQL, but it is not as easy to do so for eZPlatform 1 and 2.
We should make it easy to run test on Postgres for all eZ versions

Check out the best way to set up a webserver:

• in the same container as ez or in a separate one?
• with/without varnish
• with/without https

Worst case scenario: use instead php's built-in one or the symfony-cli tool?

Also: make sure we allow the end user to specify custom routes and settings for security.yml.

A common usecase would be f.e. to set up a different error_level ...

Ideally this should be done independently of the version of php and debian in use

If the ezsystems/legacy-bridge package is installed via composer, we should make sure that eZ legacy is automatically configured to allow execution of the legacy kernel

In case the bundle being tested has special requirements (eg. connecting to a messaging system, etc)

Possible advantage: centos and ubuntu are part of the recommended setups for Ibexa 3. Also, centos is close to amazon linux.

Probable disadvantage: this feature is most likely extremely costly in development and maintenance time...

Travis in a box :-)

Recent versions of Docker are introducing support for running docker-compose stacks directly on aws / azure / gcp.

It seems worthy to investigate how hard it would be to make the euts stack capable of running in the cloud...

First step is probably making the 'container build' phase optionally happen during the 'bootstrap' phase