Download the PHP package apsg/multisite without Composer

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

Example code of apsg/multisite

Informations about the package multisite

Multisite

Latest Version on Packagist Total Downloads Build Status StyleCI Status

Package for managing multiple installations of the same code base. It gives the ability to change the views depending on the "domain" but preserving the backend core the same.

It also lets you to define domain-specifig config.

Installation

Via Composer

Usage

After the installation:

Add your domain to your .env file, i.e.:
Add view folder

Create new view folder for your domain:

And that's it! From now on the Laravel's view engine would look for view files in main view directory (resources/views/) as well as in domain-specific directory (resources/views/test in the example above).

Config files and helpers

The package provides helper Facade through which one can access domain-specific configurations. One can publish default config file using:

The helper:

would return config equivallent to:

Current domain helper

To check current domain use the Facade helper:

Multisite assets

To compile your assets in your webpack.mix.js add something like that:

This will search automatically for files resources/js/{domain}.js and resources/sass/{domain}.scss, compile them and move them to directories public/js/{domain}.js and public/css/{domain}.css respectively.

Then one can use helpers provided with this package to automagically load in your layout file only domain-related files:

Testing

License

license. Please see the license file for more information.

All versions of multisite with dependencies

PHP Build Version
Package Version
Requires illuminate/support Version ~5|~6
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 apsg/multisite contains the following files

Loading the files please wait ....