geggleto/hydra

Container Application Framework

Maintainers

Details

github.com/geggleto/hydra

Source

Issues

Installs: 6

Dependents: 0

Suggesters: 0

Security: 0

Stars: 1

Watchers: 3

Forks: 0

Open Issues: 0

dev-master 2016-05-10 20:17 UTC

Requires

MIT 26e8a40b8b2b175be6880cd1663a27ae6cd6e294

  • Glenn Eggleton <geggleto.woop@gmail.com>

This package is auto-updated.

Last update: 2024-03-29 03:07:25 UTC

README

Container Application Framework

Setup

  • Web root of your web server should be www/

Install

  • php composer.phar create-project geggleto/hydra [your-project-name]

Example

  • See www/auth/index.php

Container Access in sub-apps

Note that the sub-apps do not have access directly to the container, this is to prevent sub-apps overwriting other module's settings. Sub-apps have read access to the container through the ContainerInterop interface.

The ContainerProxy disables the \ArrayAccess component of the container.

Todo

  • Write composer script to auto-copy the public directories to www/

Thoughts

I am not totally convinced that we should be letting modules access Slim directly since it could possibly cause overlap in some areas. The container instances should be initialized on a per sub-application basis then merged into Slim's DIC.