eZ Community » Blogs » Core Development team » Farewell eZ Publish legacy, welcome...

By

Farewell eZ Publish legacy, welcome eZ Platform

Tuesday 03 March 2015 4:59:03 pm

  • Currently 5 out of 5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Friday 13th of February turned out quite interesting for the engineering team in Lyon. In addition to being the last day before moving from an office eZ has had since 2006, we managed to merge what I think is a pretty major change: eZ Publish legacy isn't included by default anymore. In addition, eZ Platform has a prototype of its own native installer, and the new backoffice prototype, Platform UI, is now bundled by default.

"Dreaming of a brighter future" by Matthieu Aubry, used under CC BY-NC-SA 2.0 / Cropped and flipped from original.

"Dreaming of a brighter future" by Matthieu Aubry, used under CC BY-NC-SA 2.0 / Cropped and flipped from original.

 

Installation is now greatly simplified, and can be found online on ezsystems/ezplatform/INSTALL.md. In summary, installing eZ Platform from scratch is now as simple as a couple instructions:

mysql -e "create database ezplatform character set utf8"
composer create-project ezsystems/ezplatform
cd ezplatform
php ezpublish/console ezplatform:install demo
 
php ezpublish/console server:run --router bin/ezrouter.php

eZ Platform will be running on localhost:8080. Of course, you would ideally use a proper web server and virtualhost, but this works well for a quick test.

Of course, since we love backward compatibility, you can get Legacy back by requiring "ezsystems/legacy-bridge" and adding a couple lines of configuration. A detailed legacy-bridge installation procedure has been added to the documentation.

Do not forget to checkout Platform UI, the next generation backoffice. It can be accessed via the "/shell" URL. The admin account has the default "publish" password.
The infancy of Platform UI doesn't qualify it (yet) as a full featured replacement for the legacy backoffice, but those who don't need to use the backoffice on a regular basis, such as Platform or PlatformUI contributors, will feel quite a difference in installation size. Others should check it out to get a glimpse of the future. Damien's december status update about Platform UI summarizes most features.

As a bonus, the newly introduced Installer prototype is re-usable for your own needs (it is an early version, and can change at any time). All you have to do is to implement the Installer interface. It has four simple methods that handle schema, initial data, configuration and binary data. The Demo Installer example should get you kickstarted in no time. The class must then be registered as a service, and tagged with "ezplatform.installer", with a "type" attribute that will be used as the script's argument:

acme.platform_installer:
  class: Acme\Installer
  tags: 
    - { name: ezplatform.installer, type: acme }

 We hope you'll enjoy this milestone at least half as much as we do :-)

Proudly Developed with from