Download the PHP package hmphu/magemulti without Composer

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

Informations about the package magemulti

MAGENTO MULTI CLIENTS

Something that similar to Magento Go service :)

This extension allow you host multiple clients on the same Magento codebase. Every single client has their own local.xml and modules/*.xml directory. That means you can setting separate databases, caching services and modules per clients.

I. Installation

Via modman

Via composer

II. Structure

Every clients will have seperate config, media, cache, report, ... directories under the clients directory. This prevents file collisions and lets you use a single CDN domain.

Config directories

Media directories

Var directories

III. Server settings

1) The CLIENT_CODE environment variable

To make Magento work with the correct database and client's folder I had to modify the index.php and Mage.php files. This is done by two git patches in this repository and it will checks the CLIENT_CODE variable to know wich client this visited site is.

See index.php Mage::app()/Mage::run() is intialized.

2) NGINX configuration

Most of this is typical Magento Nginx config. The important lines are: fastcgi_param CLIENT_CODE foostore;

3) APACHE configuration

Most of this is typical Magento Apache config. The important lines are: SetEnv CLIENT_CODE foostore

When you setup new domain and visit the site it will open the Magento Installation page and you can continue setup your magento site. The module will create new directories and new local.xml file under the clients folder

IV. CRON configuration

Because Magento need to known the CLIENT_CODE to run exactly site so I had to created new mcron.php and mcron.sh files. This will looks for folders in clients folder which are CLIENT_CODE

So you have to setup your crontab to run mcron.php and mcron.sh instead of the default magento files (they are cron.php and cron.sh)

Example:

V. To Do

All versions of magemulti with dependencies

PHP Build Version
Package Version
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 hmphu/magemulti contains the following files

Loading the files please wait ....