Repository

Overview

The repository is a structured directory of files. Data used by the application is stored in a repository. You must have a repository to use the application.

Each time you start the application, you are prompted for the location of the repository you wish to use. The default location is the repository you used the previous time you executed the application. You can use that repository, point to a different repository or create a new repository.

Server repository vs. client repository

If you are using the application in client/server mode, you'll have a repository on the client as well as the server. See the Networking topic for more information.

The following table discusses the difference between the server repository and the client repository

Server Client
Purpose Persistent data storage Temporary data cache to optimize performance
Structure
<Server Repository Top Level Folder>/
    AnnouncementCollections/
    Audios/
    BettingSchedules/
    Checklists/
    ChipCases/
    ChipDesigns/
    ConsoleDashboards/
    ConsoleThemes/
    HandNicknameCollections/
    HTMLPreferences/
    Images/
    Leagues/
    PayoutSchedules/
    PlayerDatabases/
    QuizQuestionCollections/
    QuotationCollections/
    RuleCollections/
    ScoringMethods/
    TableConfigurations/
    TableLayoutDefinitions/
    TerminologyCollections/
    Tournaments/
    TriviaCollections/
    ApplicationPreferences.dat
<Client Repository Top Level Folder>/
    Audios/
    ChipDesigns/
    ConsoleDashboards/
    Images/
    ApplicationPreferences.dat
Examples of information stored in "ApplicationPreferences.dat"
  • Settings for whether or not to show core components in each of the core libraries
  • Default server port
  • Player database layout preferences
  • Default server IP address
  • Default server port
Need to backup? Good idea Don't bother
Integrity checking Each time you start the application, the server repository is loaded and in integrity check is performed. If any inconsistencies are found, you are prompted to resolved them before continuing. Each time the client connects to the server, the client repository is synchronized with the server repository as needed.

The "server repository" is what you'll use most, whether you use the application standalone or in client server mode. It is the source of all content used the application.

WARNING: Do NOT delete your server repository!!

WARNING: Do NOT edit your server repository manually!!

Creating a repository

Each time you start the application, you have the opportunity to create a new repository. Just select the location and the repository will be created for you.

Repository location

The repository can live anywhere as long as the application can get to it at run time. This means that your repository can live on:

Relocating a repository

Since the repository is contained under one directory tree, it's also easy to copy it from one location to another or one system to another. To move a repository:

Editing a repository

DO NOT EDIT THE REPOSITORY BY HAND! YOU CAN CREATE DATA INCONSISTENCIES!! ONLY THE APPLICATION SHOULD EDIT THE REPOSITORY!

Do not copy files into the repository outside the application and expect them to work. You must use the import facilities of the tool to do this.

Deleting a repository

If you are sure you don't need your repository any longer, just delete the directory.

Troubleshooting

One of the big benefits of the repository is that if you run into problems it is very easy for Dr. Neau to help you troubleshoot. Just zip up the repository and email it to Dr. Neau.

Multiple repositories

It's possible to have multiple repositories, if you want.

See also