Download the PHP package xervice/core without Composer

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

Xervice: Core

Scrutinizer Code Quality Code Coverage Build Status

Core classes for Xervice services

Installation

Configuration

You need no configuration to use this package. But you can define the namespaces.

Main Projectnamespace

Usage

You can create your own Xervice packages. For that you have to use a project namespace and create a module directory. In that directory you can use some predefined patterns like Facade, Factory, DependencyProvider, Config and Client.

Structure .

If you don't need one of these classes, you can remove them.

To use your Module you can use the core locator in your application:

Dynamic Locator

There are two dynamic locator traits:

Layer

Communication -> Business -> Persistence

  1. In the communication layer you can access the communication factory
  2. In the communication layer you can access the facade from your BusinessLayer.
  3. In the BusinessLayer facade you can access the business factory
  4. In the business factory you can access the reader and writer from the persistence layer

Business and communication have their own dependency container. You can access them from the factory.

Extending

To extend a module, you can create a directory with the same name in an upper level namespace. The order of the namespaces is:

  1. Core-Namespaces in defined order (Default: Xervice)
  2. Project namespace in defined order (Default: App)

If you have an module in the Xervice namespace, you can overwrite the classes in your Projectnamespaces. And that logic you can also extend in lower projectnamespaces.

Auto generating

To generate a module you can use the xervicecli package.


All versions of core with dependencies

PHP Build Version
Package Version
Requires php Version >=7.1.0
xervice/config Version ^3.0.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 xervice/core contains the following files

Loading the files please wait ....