Download the PHP package fruit/core without Composer

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

Fruit Framework

This package is the core of Fruit Framework.

Fruit is still under development, not usable now.

What is Fruit

Fruit framework tries to restructure the configuration and helper modules into raw executable PHP code.

Explain it

Basically, Fruit converts dynamic call into static call.

The work flow when a request comes in in most web frameworks is something like

  1. Execute a special PHP script (entry point), prepare basic data like auto-loading information.
  2. Load configuration. Mostly by passing config file to a helper class.
  3. Parse the configuration, load needed modules (like router) and pass related config items to it.
  4. Find correct controller using router, and execute it.

For knowing which module is "needed", frameworks must prepare a set of data, then parse it to dynamically load the modules.

Fruit works differently.

It provides a command line tool to "compile" your configuration file into an "entry file", and provides a helper object for you to load (and initialize) needed modules on demand. Since the helper object is "generated", it needs not "prepare some data and parse it" to find out correct module you want: such logics are hard-coded in the helper object.

License

Any version of MIT, GPL or LGPL.

All versions of core with dependencies

PHP Build Version
Package Version
Requires symfony/yaml Version ~3
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 fruit/core contains the following files

Loading the files please wait ....