Taipy's Core configuration¶
In the previous chapter, the main Taipy Core concepts are defined.
Taipy Core is an application builder designed to help Python developers efficiently turn their algorithms into an interactive production-ready data-driven application.
To build such an application, the first step consists in configuring the characteristics and the desired behavior of your application and its entities.
Reminder: Config vs Entities
Throughout the documentation, configuration objects are named configs (
ScenarioConfig), while runtime objects (
Scenario) are called entities.
One thing to wrap your head around (it may not be very intuitive for everyone at first) is that the configs are really just configuration objects specifying the characteristics and behaviors of the runtime concepts they relate to. Configs can be seen as generators. Indeed, each entity is instantiated from a config. Note also that the same config can be used to instantiate multiple entities.
More details on the entities are available in the Entities chapter.
All configuration objects must be created before running Core service to avoid any conflict.
This chapter is dedicated to the configuration and focuses on the various configs objects. Its sections are organized as follows:
- Config section introduces the
Configsingleton class, the single entry point for Taipy Core configuration.
- Data node configs section describes the data nodes' configurations using
- Task configs section describes the tasks' configurations using the
- Scenario configs section describes the scenarios' configurations using the
- Core config section documents the Core configuration fields and the
- Job orchestration config section documents the configuration of the job orchestration
- Config checker section presents the configuration checkers.
- Advanced configuration section provides details on advanced configuration features, particularly the capacity to overwrite configuration fields with TOML files.