Skip to content

Latest commit

 

History

History
52 lines (32 loc) · 2.24 KB

index.md

File metadata and controls

52 lines (32 loc) · 2.24 KB

🎉 Naryo Configuration

Naryo supports flexible configuration mechanisms. The core module requires manual configuration through custom implementation due to its framework-agnostic design and wide configuration domain. Configuration can be loaded from different sources thanks to the implementation of the SourceProvider interface.

Configuration Sources

Naryo allows you to use multiple configuration sources, which are resolved based on the priority of each source.

Currently, two configuration sources are supported:

  • Core

    • The spring-core module allows traditional Spring Boot configuration using YAML or .properties files, based on the EnvironmentProperties model.

  • MongoDB

    • The persistence-spring-mongo module enables dynamic configuration loading from MongoDB, based on each domain's model.

  • JPA

    • The persistence-spring-jpa module enables dynamic configuration loading from the SQL Database of your choice, based on each domain's model.

How is priority handled?

In order to manage configurations flexibly, Naryo implements a priority system among configuration sources. Priority is defined as follows:

  • persistence-spring-mongo (Priority 0): Configuration stored in MongoDB has the highest priority. If a property is defined in both MongoDB and application.yml, Naryo will take the value from MongoDB.
  • spring-core (Priority 1): The configuration in the application.yml file has secondary priority. If a property is not defined in MongoDB, the value will be taken from application.yml.

📚 Core Configuration Overview

Core Configuration Overview

📚 Mongo Configuration Overview

Mongo Configuration Overview

📚 JPA Configuration Overview

JPA Configuration Overview

👈 Previous steps

  1. Getting Started

👉 Next steps

  1. Tutorials