Download the PHP package ongr/settings-bundle without Composer

ONGR Settings Bundle

Settings Bundle provides settings API and simple user interface for setting management.

What's inside:

• Settings features toggle (for features on/off).
• Personal settings for every user, that only he can change (cookie based).
• API for every setting control.
• Simple and minimal web interface.
• Multi type settings: yaml, boolean, text.
• Cache layer for global settings.

This bundle is independent from ONGR platform and can be used in your project on its own with few dependencies.

If you need any help, stack overflow is the preferred and recommended way to ask questions about ONGR bundles and libraries.

Documentation

The online documentation of the bundle can be found in http://docs.ongr.io. Docs source is stored within the repo under Resources/doc/, so if you see a typo or problem, please submit a PR to fix it!

For contribution to the documentation you can find it in the contribute topic.

Installation

Step 1: Install Settings bundle

FilterManager bundle is installed using Composer.

Please note that settings bundle requires Elasticsearch bundle, guide on how to install and configure it can be found here.

Step 2: Enable ONGR bundles

Register Settings bundle and all required dependencies in your AppKernel:

Step 3: Add configuration

Add minimal configuration for Elasticsearch bundle. With these configs all settings will be saved to separate Elasticsearch index named settings.

If you already using ONGR Elasticsearch bundle, merge your current configuration with this one: add settings connection to your current list of connections and add settings manager to current list of managers. Read more about ElasticsearchBundle configuration.

Also add routing configuration for settings API and web interface.

Under /settings there will be all the parts of urls for settings management. For example general settings panel will be at /settings/general_settings_list and personal settings panel at /settings/settings. You can change map prefix as you like.

Under /s/ in public route map there will be a route for settings profile enabling by link. This is a landing page to enable or disable profile for the user. It's up to you to secure this prefix or not. You can map both resources under the same prefix, there will never be the same routes in both of them.

Step 4: Create index and install assets

Create an Elasticsearch index by running this command in your terminal:

More info about all commands can be found in the Elasticsearch bundle commands chapter.

We strongly recommend to have a separate index for your settings (as in example above) so your business data won't mix up with settings.

Web interface won't work without assets. Install them by using this command in your terminal:

Step 5: Check how it works

Yes, you can check how it works, but it is NOT ready for production yet. At this moment all settings management is public. Don't forget to setup firewall and protect your_settings_prefix endpoint.

Visit /{your_settings_prefix}/settings. You should see admin panel of general settings.

Usage

Global settings.

Visit /{your_management_settings_prefix}/settings and create settings you want to use in your application. There is a selection of profiles when you create a setting. After you create a setting and want to use it in website you have to activate a profile (see profile section).

There is a Twig extension to use settings in the templates.

e.g. if you want to have features toggle you can create bool setting and use extension in if statement:

Profiles

Profiles are like grouped settings where you can enable or disable all of them at once. The setting can be assigned for multiple profiles. You can find profiles management page at /your_management_settings_prefix/profiles.

To create a profile simply create your first setting with a new profile and it will appear in the profiles page.

License

This bundle is covered by the MIT license. Please see the complete license in the bundle LICENSE file.