electro / framework
Electro framework's subsystems for the standard configuration profiles
Requires
- consolidation/robo: *
- electro/kernel: dev-latest
- guzzlehttp/guzzle: *
- hansott/psr7-cookies: *
- league/glide: *
- monolog/monolog: ^2.5
- php-kit/ext-pdo: dev-latest
- php-kit/flow: dev-latest
- php-kit/php-web-console: dev-latest
- php-kit/power-primitives: dev-latest
- psr/http-message: *
- psr/log: ^2.0
- symfony/mailer: *
- vlucas/phpdotenv: *
- dev-master / 1.0.x-dev
- v0.11.x-dev
- 0.11.0
- v0.10.x-dev
- 0.10.53
- 0.10.52
- 0.10.50
- 0.10.49
- 0.10.48
- 0.10.46
- 0.10.44
- 0.10.43
- 0.10.42
- 0.10.41
- 0.10.40
- 0.10.39
- 0.10.36
- 0.10.35
- 0.10.34
- 0.10.32
- 0.10.31
- 0.10.30
- 0.10.29
- 0.10.28
- 0.10.27
- 0.10.26
- 0.10.25
- 0.10.24
- 0.10.23
- 0.10.22
- 0.10.21
- 0.10.20
- 0.10.19
- 0.10.18
- 0.10.16
- 0.10.15
- 0.10.14
- 0.10.13
- 0.10.12
- 0.10.11
- 0.10.10
- 0.10.9
- 0.10.8
- 0.10.7
- 0.10.6
- 0.10.5
- 0.10.4
- 0.10.3
- 0.10.2
- 0.10.1
- 0.10.0
- v0.9.x-dev
- 0.9.3
- 0.9.2
- 0.9.1
- 0.9.0
- dev-latest
- dev-fixing-router
- dev-new-presets
- dev-legacy
This package is auto-updated.
Last update: 2024-10-19 12:40:18 UTC
README
The Electro framework's subsystems for the standard configuration profiles
Rebuilding the package (for framework developers)
If you make changes to any susbsystem's composer.json
, you'll need to run bin/build.php
to update the package's main composer.json
.
Otherwise, changes to the subsystems' dependencies will have no effect.
After updating the main composer.json
, you should commit the changes to Git.
Introduction
This package provides the standard framework subsystems and causes the installation of all the recommended packages for a standard framework configuration.
The standard configuration provides two profiles:
- The
WebProfile
- the standard functionality for web applications. - The
ConsoleProfile
- the standard functionality for console-based applications. - The
ApiProfile
- functionality relevant for web-based APIs (ex: REST APIs).
See the framework's documentation to know more about profiles.
Subsystems vs Plugins
This package's subsystem modules provide only the main functionality of the framework.
Some optional parts of the framework are available elsewere as plugin packages that you can install on demand. Those will provide you with ORMs, database migrations, templating engines and more.
Plese refer to the framework's documentation for instructions on how to install plugins.
Installing the framework's standard package bundle
By requiring this package on your project's composer.json
file, you will install the framework with all recommended packages for a standard configuration.
You should not install this package on an empty project, as it will be missing the underlying files and directory structure required by a fully-working application.
Use the Electro base installation as your application's starting point.
Installing a customized framework profile
In a near future, there will be more framework installation profiles available.
Alternative installation profiles will provide customized versions of the framework that may be more suitable for some scenarios. For instance, a "micro-framework" profile would install a minimum set of subsystems, with a narrower scope and tuned for maximum performance.
For now, this package is the only profile available, which consists of a set of subsystems that forn a generic web framework, suitable for most common usage scenarios.
When alternative profiles became available, you'll be able to find them on GitHub, on the electro-framework
organization.
Log viewing support
To use the lnav
command to view log files generated by the framework, type the following command to install lnav
support for the framework's default log format:
lnav -i private/packages/electro/framework/lnav.json
License
The Electro framework is open-source software licensed under the MIT license.
Electro framework - Copyright © Cláudio Silva and Impactwave, Lda.