Download the PHP package magium/mcm-common-website without Composer

On this page you can find all versions of the php package magium/mcm-common-website. 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 magium/mcm-common-website

Informations about the package mcm-common-website

Magium Configuration Manager Common Website Configuration Options

This is used in conjunction with the Magium Configuration Manager. It provides some basic configuration options that most websites will use to provides some level of customization. This could include things like website titles, copyright dates, and such. On its own, these configuration options do not make much sense to have a component like this, but when used within the context of the Magium Configuration Manager it means that all of these configuration options can be managed via a UI or CLI on the production system without having to do a deployment to change configuration options.

Installation

composer install magium/mcm-common-website

This will also install magium/configuration-manager if it has not been installed in your project yet.

Usage

First you need to configure the Magium Configuration Manager. You will find this information on its GitHub link above or on this YouTube video.

You can use the bin/magium-configuration CLI to manage the settings OR you can use the UI. The UI, however, is intended to be run from within your application because it uses the same configuration mechanisms that your application would use if it were using the MCM. However, if you want to just test out the system there is a standalone script that you can use for testing.

Your application may have different ways of wiring dependency injection and such, but if you have the MCM all wired up you would do something like this:

All versions of mcm-common-website with dependencies

PHP Build Version
Package Version
Requires magium/configuration-manager Version ^1.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 magium/mcm-common-website contains the following files

Loading the files please wait ....