Download the PHP package danmrichards/notaframework without Composer

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

Not a Framework

Latest Version Build Status Quality Score Total Downloads

This is not a framework, this is something to get things done in PHP.

This thing uses a few community packages to provide just enough functionality to do something useful.

For example Whoops is used for error handling, PHRoute for routing. To name but a few.

Installation

Installation is best handled via composer:

Alternatively, if you dislike composer for some mad reason, you can download the zip file.

Routing

Routes are defined in the src/App/Http/routes.php file. By default routing is powered by PHRoute. So see that for full documentation, but basically routes can either be defined as closures:

Or they can be defined against classes and methods, such as the 2 example routes defined in the file:

Controllers

Controllers are placed in the src/App/Controllers directory and should be namespaced under NotAFramework\App\Controllers;.

There is no rigid pattern to follow with these controllers, you can add as many dependencies, helpers and additional traits/services/interfaces you like.

The example controller src/App/Controllers/HelloWorldController.php extends the base NotAFramework\App\Controllers\Controller abstract class. This allows the Symfony Request & Reponse objects to be passed to the controller. This is good practice and will allow easier interfacing with the HTTP layer.

Dependency Injection

Container from the PHP League handles dependency injection. All services are defined in the src/App/container.php file.

A few services have been set up by default; Symfony\Component\HttpFoundation\Request and Symfony\Component\HttpFoundation\Response are defined under the core services section. These are shared dependencies meaning that a single instance will be injected across the application.

Any additional services can be added at the bottom of this file. As an example the default front end renderer, Twig, has been defined. Notice that it has been defined as an alias of the RendererInterface interface, more on this below.

See the Container documentation for more information.

Theming

By default Twig is used as the theme layer, but this can easily be substituted. Simply create a new renderer class in the src/App/Render directory which implements the NotAFramework\App\Render\RendererInterface interface. You cna then update the src/App/container.php file and controllers accordingly.

Twig, if used in file system mode, will look it's template files in the templates folder.

Tests

Yeah...all the packages are unit tested within themselves, and we have PHPUnit. So that'll do for now.

License

MIT License yo!

All versions of notaframework with dependencies

PHP Build Version
Package Version
Requires php Version ^7.1.3
filp/whoops Version ^2.0
symfony/http-foundation Version ^4.0
phroute/phroute Version ^2.1
league/container Version ^3.0
twig/twig Version ^2.0
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 danmrichards/notaframework contains the following files

Loading the files please wait ....