ems/framework

A framework agnostic php library which provides the basics for cmsable and other frameworks

v0.4.3 2022-08-17 05:38 UTC

Requires

• php: >=7.2.0
• ext-pdo: *
• psr/container: 1.*|2.0.*
• psr/http-message: 1.*
• psr/http-server-middleware: 1.*
• psr/log: ~1.0
• squizlabs/php_codesniffer: 3.*

Requires (Dev)

• ext-json: *
• fakerphp/faker: ^1.16
• illuminate/config: 5.*|6.*
• illuminate/container: 5.*|6.*
• illuminate/contracts: 5.*|6.*
• illuminate/database: 5.*|6.*
• illuminate/filesystem: 5.*|6.*
• illuminate/mail: 5.*|6.*
• illuminate/queue: 5.*|6.*
• illuminate/support: 5.*|6.*
• illuminate/validation: 5.*|6.*
• illuminate/view: 5.*|6.*
• internations/http-mock: 0.10.*|0.11.*|0.12.*|0.13.*|0.14.*
• league/flysystem: 1.*
• mockery/mockery: ~1.3
• natxet/cssmin: ~3.0
• nikic/fast-route: 1.3.*
• patchwork/jsqueeze: ~2.0
• php-coveralls/php-coveralls: 2.1.*
• phpunit/phpunit: 6.*
• swiftmailer/swiftmailer: 5.*|6.0.*
• tedivm/jshrink: ~1.1

Replaces

• ems/assets: v0.4.3
• ems/cache: v0.4.3
• ems/contracts: v0.4.3
• ems/core: v0.4.3
• ems/graphics: v0.4.3
• ems/mail: v0.4.3
• ems/model: v0.4.3
• ems/skeleton: v0.4.3
• ems/testing: v0.4.3
• ems/view: v0.4.3
• ems/x-type: v0.4.3

MIT

• Michael Tils

README

The entity management system is a collection of interfaces for common software development tasks. Its main focus is to provide architectural solutions by common interfaces and patterns to ensure a maximum maintainability in bigger software projects.

EMS is build to be used on top of other frameworks like laravel, symfony or zend. The most implementations have no framework dependency but EMS is not meant to be used alone.

EMS ensures that you rely as little as possible on any external library, even on EMS itself. One principle is that only interface methods in EMS are public and no additional methods are visible. To ensure that, a lot of interfaces have planned hooks (like Cache::onAfter('invalidate', callable $do)) to ensure its extendability without the need for inheritance or code duplication.

The state of its packages

Currently this package could be seen as in beta phase. Almost all of my customer applications are based on cmsable, which is currently ported to ems. So the code works in big and stable applications. (Big means with for example 2 Million users/month) But the interfaces are currently changing. All features are developed in a predefined chain of actions:

1. Requirement specification
2. Technical Specification
3. Implementation
4. Release
5. Documentation.

So if a package is documented it can be considered as stable.