Grooper Repository (Concept): Difference between revisions
Dgreenwood (talk | contribs) No edit summary |
Dgreenwood (talk | contribs) No edit summary |
||
| Line 5: | Line 5: | ||
This environment consists of: | 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). | 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). | ||
Revision as of 09:34, 6 October 2021
A Grooper Repository is the environment used to create, configure and execute objects in Grooper. It provides the framework to "do work" in Grooper.
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).
Creating (or connecting to) a Grooper Repository is one of the first things you will do after installing Grooper to start designing (or implementing already architected) document processing solutions. For more information on how to create or connect to a Grooper Repository, visit the Install and Setup or Grooper Config articles.