Download the PHP package masev/ezpublish-kernel without Composer

On this page you can find all versions of the php package masev/ezpublish-kernel. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package ezpublish-kernel

eZ Publish 5.x Kernel

Build Status

SensioLabsInsight

Welcome to the new eZ Publish 5.x Kernel, this code repository contains several layers of API's and implementation of them. However it does not contain all parts that make up the eZ Publish 5 install, for the full eZ Publish 5 package including bundles, Legacy Stack, install doc and more; please see our ezpublish-community repository.

Legacy Stack (LS)

Legacy Stack: Legacy kernel (4.x) + extensions

eZ Publish 5.x is a bottom up rewrite of eZ Publish, so a conservative approach where taken on backwards compatibility by bundling both Legacy Stack (4.x) and 5.x Stack together in one integrated package (ref ezpublish-community repository above).

In addition to the BC reason, the second reason is that eZ Publish 5.x does not yet provide own UI's, editor and admin gui is for the time being still provided by Legacy Stack.

The legacy integrations are done in many parts of the systems, making it possible to use both kernels in the same request, hence being able to do a smooth transition from existing 4.x installation to 5.x installation going forward.

However for performance reasons we recommend trying to use either legacy with "legacy_mode" turned on or pure 5.x Stack on a siteaccess case by case basis. This will still make sure cache and other integrations work together (something that is not the case if you point Apache directly to eZ Publish Legacy), but will avoid duplicate lookups ("fallbacks").

5.x Stack

5.x Stack: 5.x kernel + Bundles (former extensions)

Bundles

The highest level in the eZ Publish 5 architecture are bundles that builds on top of everything bellow, this is where most eZ Publish 5 Bundles will be written. They will exist in separate git repositories, and optionally defined as dependencies in your project composer.json file (see ezpublish-community repository).

5.x Kernel

Kernel Bundles: REST, Core & Legacy

These bundles are important parts of the eZ Publish 5.x kernel.

You can find these in eZ/Bundle and their lower level parts in:

Public API

Public API currently provides access to the Content Repository of eZ Publish, exposing Content, Locations (former Nodes), Sections, Content Types (former Content Classes), User Groups, Users and Roles. It also provides a new clear interface for plugging in custom field types (former Datatypes).

Public API is built on top of a set of SPI's abstracting storage/file/* functionality. By using Public API your code will be forward compatible to future releases based on enhanced, more scalable and more performant storage engines. It is also fully backwards compatible by using the included "Legacy" storage engine, which stores data in the way legacy kernel is used to finding it.

Important parts of this layer is:

(Private) SPI(Service Provider Interface)

Service Provider Interfaces are interfaces that can contain one or several implementations, in some cases Public API will only be able to use one at a time; Persistence (database), IO (file system). In other cases it expects several implementations; FieldTypes (former DataTypes), Limitations (permissions system).

SPI layer is currently considered "private" as it will still undergo changes, it will be made "final" by the time we have a fully working NoSQL implementation of Persistence and scalable IO storage implementation like S3. Meaning you can make your own implementation if you want, but we don't guarantee that it will work across versions.

Currently SPI consists of:

How to run tests

Dependencies

You can also run tests (slower) on mysql or postgres, see .travis.yml for how.

Installation

This should produce similar result as travis. If you don't double check .travis.yml for up-to-date info on how travis is setup.

Issue tracker

Submitting bugs, improvements and stories is possible on https://jira.ez.no/browse/EZP

Contributing

eZ Publish 5.x is a fully open source, community-driven project, and code contributions are simply done via github pull requests.

Short:

For further information please have a look at the related guidance page. You will, amongst other, learn how to make pull-requests. More on this here : "How to contribute to eZ Publish using GIT".

Discussing/Exchanging

A dedicated forum has been set-up to discuss all PHP API-related topics : http://share.ez.no/forums/new-php-api

Copyright & license

Copyright eZ Systems AS, for copyright and license details see provided LICENSE file.

All versions of ezpublish-kernel with dependencies

PHP Build Version
Package Version
Requires php Version >=5.3.3
ext-ctype Version *
ext-fileinfo Version *
ext-gd Version *
ext-intl Version *
ext-json Version *
ext-mbstring Version *
ext-pdo Version *
ext-spl Version *
ext-xsl Version *
zetacomponents/mail Version ~1.8
zetacomponents/php-generator Version ~1.1
symfony/symfony Version ~2.3
symfony-cmf/routing Version 1.1.*
qafoo/rmf Version 1.0.*
kriswallsmith/buzz Version >=0.9
tedivm/stash-bundle Version 0.4.*
sensio/distribution-bundle Version ~2.3
nelmio/cors-bundle Version 1.3.*
pagerfanta/pagerfanta Version ~1.0
doctrine/dbal Version 2.5.*@beta
ocramius/proxy-manager Version 0.5.*
doctrine/doctrine-bundle Version 1.3.*@beta
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package masev/ezpublish-kernel contains the following files

Loading the files please wait ....