PHPackages                             magium/mcm-common-website - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. magium/mcm-common-website

ActiveLibrary

magium/mcm-common-website
=========================

Some common website configuration options for use with the Magium Configuration Manager

1.0.0(9y ago)034Apache-2.0

Since May 8Pushed 9y ago1 watchersCompare

[ Source](https://github.com/magium/mcm-common-website)[ Packagist](https://packagist.org/packages/magium/mcm-common-website)[ RSS](/packages/magium-mcm-common-website/feed)WikiDiscussions master Synced today

READMEChangelog (1)Dependencies (1)Versions (2)Used By (0)

Magium Configuration Manager Common Website Configuration Options
=================================================================

[](#magium-configuration-manager-common-website-configuration-options)

This is used in conjunction with the [Magium Configuration Manager](https://github.com/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
============

[](#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
=====

[](#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](https://www.youtube.com/watch?v=76MLD9Kl2Lk).

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](https://github.com/magium/configuration-manager/tree/develop/tests/View/standalone).

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:

```