> **Licensing:** this add-on is a thin wrapper licensed under **Apache 2.0**. It contains no code of its own and simply pulls in the **Configuration Manager AppJar** modules, which are **commercial software** distributed under the [AppJars Software License Agreement](https://www.appjars.com/legal/license/v1/). You can use Configuration Manager for free in **free mode** (up to 5 system and user configurations combined, not counting the `com.appjars.*` entries the AppJars read themselves). A license removes all limits. See [Licensing](https://docs.appjars.com/licensing/). **Configuration Manager** stores your application's configuration values in the database and lets you manage them at runtime, with an administration UI built with Vaadin Flow. Adjust timeouts, limits, feature toggles or display preferences without editing files or redeploying, and keep a complete record of who changed what and when. ## Features - **System and user scopes:** *system configurations* hold one value shared by the whole application, while *user configurations* let each user keep their own value, falling back to the default. - **Database-backed Spring properties:** system configurations are exposed as a Spring `PropertySource`, so a matching name can satisfy `@Value` placeholders and `Environment` lookups, overriding `application.properties`. - **Runtime changes:** updated values are visible to `Environment` lookups right away; an opt-in application-context restart applies them to injected `@Value` fields too. - **Full value history:** saving a value never overwrites the previous one, so administrators and users can review past values, see who set them and restore any of them. - **Typed values:** each configuration declares its data type (string, integer, decimal, boolean, date or time), which drives how its value is stored and validated. - **Ready-made views:** *System Configurations* and *User Configurations* for administrators and *My Configurations* for end users, with filters by name, description and type. ## Installation If your project doesn't declare it yet, add the Vaadin add-ons repository: ```xml vaadin-addons https://maven.vaadin.com/vaadin-addons ``` Add the dependency. The wrapper declares the AppJars repository (`https://maven.appjars.com`), so Maven resolves the modules automatically: ```xml org.vaadin.addons.appjars appjars-configuration-manager 2.0.1 ``` - **Gradle** ignores repositories declared in dependency POMs, so add `maven { url "https://maven.appjars.com" }` to your repositories. - **Nexus/Artifactory mirroring everything (`mirrorOf *`):** your administrator needs to add a proxy for `https://maven.appjars.com`. Then follow the [Getting started guide](https://docs.appjars.com/configuration-manager/getting-started/). ## Requirements - Java 21 - Vaadin 25.2 - Spring Boot 4.1 - A `UserProvider` bean supplied by your application, which returns the current username and the list of users ([details](https://docs.appjars.com/configuration-manager/developer-guide/#required-integration-userprovider)) - JPA / Hibernate ## Included dependencies | Artifact | License | |---|---| | `com.appjars:appjars-configuration-manager-flow` | AppJars Software License Agreement v1 (commercial) | | `com.appjars:appjars-configuration-manager-business-impl` | AppJars Software License Agreement v1 (commercial) | | `com.appjars:appjars-configuration-manager-data-impl` | AppJars Software License Agreement v1 (commercial) | These modules transitively bring in the rest of the Configuration Manager modules and `appjars-*-utils` (same commercial license), plus open-source libraries such as Vaadin add-ons by Flowing Code (Apache 2.0). ## Links - [Product page](https://www.appjars.com/catalog/configuration-manager/) - [Documentation](https://docs.appjars.com/configuration-manager/overview/) - [Demo application](https://github.com/AppJars/configuration-manager-demo) - [Licensing and free mode](https://docs.appjars.com/licensing/) AppJars are built and maintained by [Flowing Code](https://www.flowingcode.com).