nti/config-bundle

Database-stored settings made available via a service for your Symfony project.

Thursday, February 1, 2018
by ntidev
Repository
1 Watchers
0 Stars
5 Installations

PHP
0 Dependents
0 Suggesters
27 Forks
0 Open issues
16 Versions
0 % Grown

The README.md

Information

, _(*1)

CraueConfigBundle manages configuration settings stored in the database and makes them accessible via a service in your Symfony project. These settings are similar to those defined in parameters.yml but can be modified at runtime, e.g. by an admin user., _(*2)

Installation

Get the bundle

Let Composer download and install the bundle by running, _(*3)

php composer.phar require craue/config-bundle:~2.1

in a shell., _(*4)

Enable the bundle

// in app/AppKernel.php
public function registerBundles() {
    $bundles = array(
        // ...
        new Craue\ConfigBundle\CraueConfigBundle(),
    );
    // ...
}

Create the table

Preferably you do this by calling, _(*5)

# in a shell (run `bin/console` instead of `app/console` if your project is based on Symfony 3)
php app/console doctrine:migrations:diff
php app/console doctrine:migrations:migrate

or, _(*6)

# in a shell (run `bin/console` instead of `app/console` if your project is based on Symfony 3)
php app/console doctrine:schema:update

or however you like., _(*7)

Add the route to manage settings (optional)

You can either import the default routing configuration, _(*8)

# in app/config/routing.yml
craue_config_settings:
  resource: "@CraueConfigBundle/Resources/config/routing/settings.xml"
  prefix: /settings

...or add your own to have full control over the URL pattern., _(*9)

# in app/config/routing.yml
craue_config_settings_modify:
  path: /settings/modify
  defaults:
    _controller: CraueConfigBundle:Settings:modify

Usage

Defining settings

This bundle does not provide functionality to create new settings because this would make no sense at runtime. Those settings will be used in your application and thus code needs to be written for that. This means that you have to create new settings in the database table craue_config_setting yourself, e.g. using a migration., _(*10)

Managing settings' values

If you added the route described above you can manage the values of all defined settings in a simple form. By default, you can access that form by browsing to app_dev.php/settings/modify. But you probably want to limit access to this form in your security configuration., _(*11)

Reading settings

The bundle provides a service called craue_config. Inside of a controller you can call, _(*12)

$this->get('craue_config')->get('name-of-a-setting')

to retrieve the value of the setting name-of-a-setting. Furthermore, you can call, _(*13)

$this->get('craue_config')->all()

to get an associative array of all defined settings and their values., _(*14)

$this->get('craue_config')->getBySection('name-of-a-section')

will fetch only settings with the specified section (or those without a section if explicitly passing null for the name)., _(*15)

Writing settings

With the same service you can set new values of settings:, _(*16)

$this->get('craue_config')->set('name-of-a-setting', 'new value');
$this->get('craue_config')->setMultiple(array('setting-1' => 'foo', 'setting-2' => 'bar'));

Keep in mind that the setting has to be present, or an exception will be thrown., _(*17)

Usage in Twig templates

The Twig extension in this bundle supports reading settings directly in your template., _(*18)

{{ craue_setting('name-of-a-setting') }}

Enable caching (optional)

To reduce the number of database queries, you can set up a cache for settings. First, you have to choose which cache implementation you'd like to use. Currently, there are adapters available for: - DoctrineCacheBundle - Symfony Cache component, _(*19)

Refer to the documentation of each implementation for details and read on in the corresponding section below. When done, CraueConfigBundle will automatically cache settings (using the built-in craue_config_cache_adapter service)., _(*20)

Keep in mind to clear the cache (if needed) after modifying settings outside of your app (e.g. by Doctrine migrations):, _(*21)

# in a shell (run `bin/console` instead of `app/console` if your project is based on Symfony 3)
php app/console doctrine:cache:clear craue_config_cache

Cache implementation: DoctrineCacheBundle

Set the parameter craue_config.cache_adapter.class appropriately and configure a so-called cache provider with the alias craue_config_cache_provider:, _(*22)

# in app/config/config.yml
parameters:
  craue_config.cache_adapter.class: Craue\ConfigBundle\CacheAdapter\DoctrineCacheBundleAdapter

doctrine_cache:
  providers:
    craue_config_cache:
      apc: ~
      namespace: craue_config
      aliases:
        - craue_config_cache_provider

Cache implementation: Symfony Cache component

Set the parameter craue_config.cache_adapter.class appropriately and configure a so-called cache pool with the service id craue_config_cache_provider:, _(*23)

# in app/config/config.yml
parameters:
  craue_config.cache_adapter.class: Craue\ConfigBundle\CacheAdapter\SymfonyCacheComponentAdapter

services:
  craue_config_cache_provider:
    class: Symfony\Component\Cache\Adapter\FilesystemAdapter
    public: false
    arguments:
      - 'craue_config'
      - 0
      - '%kernel.cache_dir%'

Customization

Redirect to a different page after submitting the built-in form

If you've enabled the build-in form, you can define where to redirect on successfully saving the changes by setting the target route name:, _(*24)

# in app/config/parameters.yml
parameters:
  craue_config.redirectRouteAfterModify: craue_config_settings_modify

Rendering of settings in sections

If you want to render settings in a group (called section here), you'll have to assign those settings a common section name (in the database). Optionally, you can influence the order of these sections:, _(*25)

# in app/config/parameters.yml
parameters:
  craue_config.configTemplate.sectionOrder: [section1, section2, section3]

Settings without a section will be rendered at first. Sections without explicit ordering are rendered at last., _(*26)

Translation

You can add translations for all settings (and sections) to be shown in the form by adding them to translation files with the CraueConfigBundle domain, e.g., _(*27)

# in app/Resources/CraueConfigBundle/translations/CraueConfigBundle.en.yml
name-of-a-setting: name of the setting

# in app/Resources/CraueConfigBundle/translations/CraueConfigBundle.de.yml
name-of-a-setting: Name der Einstellung

Using a custom entity for settings

The custom entity has to provide a mapping for the field value. The class BaseSetting defines this field, but no mapping for it. This allows easy overriding, including the data type. In the following example, the value field will be mapped to a text column, which will in turn render the built-in form fields as textarea., _(*28)

So create the entity and its appropriate mapping:, _(*29)

// src/MyCompany/MyBundle/Entity/MySetting.php
use Craue\ConfigBundle\Entity\BaseSetting;
use Doctrine\ORM\Mapping as ORM;

/**
 * @ORM\Entity(repositoryClass="Craue\ConfigBundle\Repository\SettingRepository")
 * @ORM\Table(name="my_setting")
 */
class MySetting extends BaseSetting {

    /**
     * @var string|null
     * @ORM\Column(name="value", type="text", nullable=true)
     */
    protected $value;

    /**
     * @var string|null
     * @ORM\Column(name="comment", type="string", nullable=true)
     */
    protected $comment;

    public function setComment($comment) {
        $this->comment = $comment;
    }

    public function getComment() {
        return $this->comment;
    }

}

And make the bundle aware of it:, _(*30)

# in app/config/config.yml
craue_config:
  entity_name: MyCompany\MyBundle\Entity\MySetting

The Versions

01/02 2018

dev-master

9999999-dev https://github.com/craue/CraueConfigBundle

Database-stored settings made available via a service for your Symfony project.

symfony-bundle config-bundle

Database-stored settings made available via a service for your Symfony project.

nti/config-bundle

The README.md

Information

Installation

Get the bundle

Enable the bundle

Create the table

Add the route to manage settings (optional)

Usage

Defining settings

Managing settings' values

Reading settings

Writing settings

Usage in Twig templates

Enable caching (optional)

Cache implementation: DoctrineCacheBundle

Cache implementation: Symfony Cache component

Customization

Redirect to a different page after submitting the built-in form

Rendering of settings in sections

Translation

Using a custom entity for settings

The Versions

dev-master

The Requires

The Development Requires

by Symfony Community

by Christian Raue

2.1.0

The Requires

The Development Requires

by Symfony Community

by Christian Raue

2.0.0

The Requires

The Development Requires

by Symfony Community

by Christian Raue

1.4.2

The Requires

The Development Requires

by Symfony Community

by Christian Raue

1.4.1

The Requires

The Development Requires

by Symfony Community

by Christian Raue

1.4.0

The Requires

The Development Requires

by Symfony Community

by Christian Raue

1.3.2

The Requires

The Development Requires

by Symfony Community

by Christian Raue

1.3.1

The Requires

The Development Requires

by Symfony Community

by Christian Raue

1.3.0

The Requires

The Development Requires

by Symfony Community

by Christian Raue

1.2.0

The Requires

by Symfony Community

by Christian Raue

1.1.4

The Requires

by Symfony Community

by Christian Raue

1.1.3

The Requires