Some cut&paste from maillinglist

Currently, after downloading the bundle you have to do quite a lot (
https://github.com/ezsystems/ezpublish5/blob/master/INSTALL.md ) before it up
and running, compared to ezp 4.x which was just to extract in a directory and
create a virtualhost....

jv : This should be simplified with a custom composer installer (or pre-installation from package) + modified setup wizard. Still pending task.

#2 Also, of you are going to use the public api, you have to do a lot more (
not mentioned in the INSTALL.md:

• copy config.php-DEVELOPMENT to config.php
• $ composer install --dev
• fix ezp5/app/ezpublish_legacy/settings/override/service.ini to disable in-
  memory storage
  jv : This part is for API dev only (running tests), NOT for end customers/developers.
  vl : hmm.. no convinced.. needs to be invesigated

#3 the "B: From GIT Development ONLY" should removed from INSTALL.md. It
doesn't apply to Enterprise customers. Also, the installation doc should be
placed somewhere else as well, right ? doc.ez.no, confluence or wherever?
jv : Yes it should take place on Confluence

According to the eZ Publish Kilimanjaro 5.0 Deliverables, the public API is
supposed to be included in the bundle ( the step "$ composer install --dev",
seems to violate this, doesn't it ? )
IMO, it should not be needed to run any composer stuff at all after downloading
the bundle. Is this not possible to achieve ?
jv : Running Composer should not be needed with full package, indeed and yes, this is possible to achieve (build stuff)