Download the PHP package contenir/contenir-workflow-mezzio without Composer

On this page you can find all versions of the php package contenir/contenir-workflow-mezzio. 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 contenir-workflow-mezzio

contenir/contenir-workflow-mezzio

Formerly contenir/contenir-workflow; the old package is abandoned in favour of this one.

Continuous Integration codecov

Database-driven workflow system for Mezzio that generates routes and navigation from a hierarchical page structure, for Contenir CMS.

Your application supplies a tree of resources (pages, articles, ...). For each resource a workflow decides its route (path, middleware, defaults) and its navigation page (label, sitemap change frequency and priority). The ResourceStrategy walks the tree once, caches the result, and the routes are registered with the Mezzio Application either when it is created (delegator factory) or on the first request (middleware).

Requirements

The 0.x release remains available from the 0.x branch and the v0.1.0 tag; see UPGRADE-2.0.md.

Install

With laminas-component-installer the Contenir\Workflow\ConfigProvider is added to your configuration automatically. It registers ResourceStrategy, WorkflowPluginManager and WorkflowMiddleware.

Usage

1. Implement ResourceInterface on your entity

2. Provide the resource tree with a ResourceAdapterInterface

3. Configure the workflow manager

4. Handle the routed request

Each route carries the resource's primary keys as the id default, which the router passes to the request as an attribute:

Public API

Class Purpose
ResourceInterface A routable resource: slug, primary keys, type, id, children
Repository\ResourceAdapterInterface Supplies the top-level resources
Workflow\WorkflowInterface Turns one resource into a route config and a navigation config
Workflow\AbstractWorkflow Base workflow: route id <type>-<id>, path from slug, navigation defaults
Workflow\AbstractPageWorkflow Page route logic: routes a resource to its own getMiddleware() (or $middleware)
Workflow\PageWorkflow The default page workflow (final): monthly, priority 0.6
Workflow\WorkflowPluginManager Plugin manager for workflows (page, Page, PageWorkflow)
Workflow\WorkflowFactory Factory for workflows with a no-argument constructor
Strategy\ResourceStrategyInterface getRouteConfig(), getNavigationConfig(), clearCache()
Strategy\AbstractResourceStrategy Walks the tree and caches; extend it to customise (getWorkflowType(), getNavigationPage())
Strategy\ResourceStrategy The default strategy (final)
Factory\WorkflowApplicationDelegatorFactory Registers the routes when the Application is created
Middleware\WorkflowMiddleware Registers the routes on the first request instead
ConfigProvider and the Factory\* classes Container wiring

Every concrete class is final; the abstract classes and interfaces above are the extension points.

The docs folder covers each area in detail:

Development

The QA toolchain is contenir/contenir-qa-tools. Mago is a standalone binary, installed separately (brew install mago).

License

MIT. See LICENSE.


All versions of contenir-workflow-mezzio with dependencies

PHP Build Version
Package Version
Requires php Version ~8.3.0 || ~8.4.0 || ~8.5.0
laminas/laminas-cache Version ^3.12
laminas/laminas-cache-storage-adapter-filesystem Version ^2.4
laminas/laminas-diactoros Version ^3.3
laminas/laminas-servicemanager Version ^3.22
mezzio/mezzio Version ^3.18
psr/container Version ^1.1 || ^2.0
psr/http-message Version ^1.1 || ^2.0
psr/http-server-handler Version ^1.0.2
psr/http-server-middleware Version ^1.0.2
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 contenir/contenir-workflow-mezzio contains the following files

Loading the files please wait ...