Download the PHP package meysampg/espricho without Composer
On this page you can find all versions of the php package meysampg/espricho. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download meysampg/espricho
More information about meysampg/espricho
Files in meysampg/espricho
Package espricho
Short Description A ready to use modular framework (like Yii2) with a powerful container (like Laravel) for php
License MIT
Informations about the package espricho
Espricho [ABANDONED]
🟥⚠️ THIS PACKAGE IS ABANDONED. PLEASE SELECT ANOTHER PACKAGE OR FORK THIS REPOSITORY AND INFORM ME ON p.g.meysam [at] Gmail [dot] com TO REFER TO YOUR PACKAGE IN PACKAGIST ⚠️🟥
Espricho is a lightwieght framework for php7, based on Symfony components with a built-in modular system support.
Prevision!
Espricho is heavily inspired from Laravel and Yii2. Its modularity is similar to Yii2 but thanks to the Symfony DI container, it has a powerful container like Laravel! Espricho is the Persian name of swallow bird (in Kermani dialect).
Mafsho
mafsho
is a command line tool which provide a lot of functionality
like generators to work more easier with Espricho. It's a Farsi word
means bag (in Kermani dialect). You can run it with php mafsho
command.
Structure
Espricho has a structure like this:
We talk about each one in continue.
Configurations VS Environmental Variables
Espricho supports definition of environmental variables (variables which are
depended on the running environment). You should put them on .env
(or .env.dist
which dist
is an application stage) file. It's a good idea if all keys on the .env
file be upper case and start with the section name. For example, all ElasticSearch keys
starts with ELASTICSEARCH_
prefix.
On other side, you can define application
level configurations in the Config/*.yaml
files. Finally both of this
configurations are accessible from sys()->getConfig('dot.notationed.key', 'default')
.
sys.yaml
On sys.yaml
file, you could set the boot parameters of the system. As the
main result, you could define system module loaders under the loader
key.
Database Configurations
The database configuration should be set on .env
the root of the project.
A sample for its content is similar
to this:
Modules
For defining module, you must put your module under the
Modules
folder and define your structure on it. A sample
structure can be something like this:
Each module has its own route definition rules and they must
be defined on routes.yaml
file under Configs
category.
After definition of module, you can register it on modules.yaml
in Configs
folder of the project's root. A sample
content for this configuration file is:
Each module can have its submodules and they must be defined on
modules.yaml
file in Configs
folder of the module directory.
Definition of routes is similar.
All versions of espricho with dependencies
symfony/cache Version ^4.2
symfony/security Version ^4.2
symfony/routing Version ^4.2
symfony/serializer Version ^4.2
symfony/validator Version ^4.3
symfony/options-resolver Version ^4.2
symfony/http-foundation Version ^4.2
symfony/http-kernel Version ^4.2
symfony/dependency-injection Version ^4.2
symfony/yaml Version ^4.2
symfony/event-dispatcher Version ^4.2
symfony/debug Version ^4.2
doctrine/collections Version ^1.6
symfony/console Version ^4.2
nesbot/carbon Version ^2.18
lcobucci/jwt Version ^3.3
monolog/monolog Version ^1.24
doctrine/annotations Version ^1.6
symfony/property-info Version ^4.3
doctrine/cache Version ^1.8
ext-json Version ^1.7
predis/predis Version ^1.1
elasticsearch/elasticsearch Version ^6.7
guzzlehttp/guzzle Version ~6.0