Grooper Repository (Concept): Difference between revisions
Configadmin (talk | contribs) Created page with "An environment consisting of a database connection and a file store location. These repositories are where data regarding Grooper processes and content creation are stored a..." |
No edit summary |
||
| (17 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<blockquote>{{#lst:Glossary|Grooper Repository}}</blockquote> | |||
This environment consists of: | |||
# a database connection and | |||
# a file store location. | |||
The database stores Grooper nodes and their property settings (such as a '''Content Model''' or a '''Data Type''' or any other Grooper object). The file store location houses content associated with these nodes (such as the image file for a '''Batch Page''' object). | |||
=== For more information === | |||
* [[Install_and_Setup#Creating_a_new_Grooper_Repository|How to create a new Grooper Repository]] | |||
* [[Install_and_Setup#Connecting_to_an_existing_Grooper_Repository|How to connect to an existing Grooper Repository]] | |||
* [[Grooper Infrastructure#Grooper Repository details|Grooper Repository details (includes a list of tables in the Grooper Database)]] | |||
Latest revision as of 14:45, 21 November 2024
A Grooper Repository is the environment used to create, configure and execute objects in Grooper. It provides the framework to "do work" in Grooper. Fundamentally, a Grooper Repository is a connection to a database and file store location, which store the node configurations and their associated file content. The Grooper application interacts with the Grooper Repository to automate tasks and provide the Grooper user interface.
This environment consists of:
- a database connection and
- a file store location.
The database stores Grooper nodes and their property settings (such as a Content Model or a Data Type or any other Grooper object). The file store location houses content associated with these nodes (such as the image file for a Batch Page object).