Download the PHP package davidecesarano/embryo without Composer

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

Embryo Framework 3 skeleton application

You can use this skeleton application to start working on a new Embryo Framework 3 application.

Getting Started

Requirements

Installation

Using Composer:

Configuration

Embryo utilizes the DotEnv PHP library. In a fresh Embryo installation, the root directory of your application will contain a .env.example file. When you install Embryo via Composer, this file will automatically be renamed to .env.

Directory Structure

Directory Description
app Contains the core code of your application. This directory contains a variety of additional directories such as Controllers, Exceptions, Helpers, Middleware, Models and Services.
bootstrap Contains the files which bootstraps your application such as app instantiation, middleware, services and settings.
public Contains the entry point for all request (index.php file) and the assets directory.
routes Contains all of the route definitions for your application. By default, several route files are included with Embryo: app.php and api.php.
storage Contains your logs (logs), compiled templates file (views), file based sessions (sessions), caches files (cache).
translations Contains your language files.
views Contains the views files.

Concepts

Life Cycle

PSR-7

Embryo supports PSR-7 interfaces for its Request and Response objects.

Middleware

You can run code before and after your Embryo application to manipulate the Request and Response objects as you see fit. This is called middleware. A middleware implements the PSR-15 Middleware Interface.

Dependency Container

Embryo uses an dependency container to prepare, manage, and inject application dependencies. Embryo supports containers that implement PSR-11.

Application

Routing

You can define application routes using the application instance’s routing methods. Every method accepts two arguments:

Embryo Routing supports GET, POST, PUT, PATCH, DELETE and OPTIONS request methods. Every request method corresponds to a method of the Router object: get(), post(), put(), patch(), delete() and options(). You can use all() and map() methods for supporting all methods or specific route methods.

See full documentation: Embryo Routing.

Register route files

All Embryo routes are defined in your route files, which are located in the routes directory. These files are automatically loaded by your application in boostrap/app.php file. If you want create new ruote file, add it in routes directory and register it in import() method of the application instance in boostrap/app.php file:

Middleware

In Embryo you may create a PSR-15 middleware in app\Middleware directory. You may add middleware to application, to specific route or to route group.

Application middleware

If you want register middleware for every HTTP request, add application middleware in bootstrap\middleware.php. The addMiddleware() method accepts a string, an array or an instance of Psr\Http\Server\MiddlewareInterface.

Route middleware

You can use the middleware() method to assign one or more middleware at the route. The middleware() method accepts a string, an array or an instance of Psr\Http\Server\MiddlewareInterface.

Route group middleware

In addition to the routes, you can assign one or more middleware to a group and to individual routes within the group. The middleware() method accepts a string, an array or an instance of Psr\Http\Server\MiddlewareInterface.

Controllers

Instead of defining all of your request handling logic as closures in your route files, you may wish to organize this behavior using "controller" classes. Let's take a look at an example of a basic controller. Note that the controller extends the base controller class included with Embryo:

You can define a route to this controller method like so:

Controllers are required to extend a base class. However, you will not have access to features such as the get(), request() and response() methods.

Dependency Injection & Controllers

You are able to type-hint any dependencies your controller may need in its constructor. The declared dependencies will automatically be resolved and injected into the controller instance:

In addition to constructor injection, you may also type-hint dependencies on your controller's methods:

In addition, you may also to use the get() method of the base controller class:

Base controller class also has access to PSR-7 request() and response() methods:

Alternatively, you may to access to request() and response() helpers:

Service Providers

Service providers are the central place of all Embryo application bootstrapping. Your own application, as well as all of Embryo's core services, are bootstrapped via service providers.

Writing a service

The service providers era located in app/Services directory. All service providers extend the Embryo\Container\ServiceProvider class and contains a register method. Within the register method, you should only bind things into the service container.

Registering a service

Models

Views

Packages

Validation


All versions of embryo with dependencies

PHP Build Version
Package Version
Requires php Version >=7.2
davidecesarano/embryo-framework Version ~3.0
vlucas/phpdotenv Version v2.5.1
phpmailer/phpmailer Version ~6.0
firebase/php-jwt Version ^5.3
league/flysystem Version ^2.1
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 davidecesarano/embryo contains the following files

Loading the files please wait ....