FullCount Subversion Repositories
Introduction
Subversion is a software tool for organizing and managing different versions of source code for computer programs. It is primarily used for managing plain text files such as source code, configuration files, or scripts; however, it can be used to store different versions of binary files such images, (small) applications, Microsoft Office documents, WAR files, etc. For a much more thorough introduction to Subversion, please consider reading Version Control with Subversion.
Tools
FullCount uses a tool called TortoiseSVN to work with Subversion repositories. TortioseSVN is only available for Microsoft Windows; however, other Subversion clients are available for other operating systems.
Repositories
FullCount Subversion repositories are stored on sourcecontrol.fullcount.net. Anyone logged into the VPN can view files; however, you'll need an account to view older versions of a file, or to save files to a repository.
|
Name |
Description |
|
Configuration files and scripts used for automating tasks on FullCount servers. |
|
|
Back office UI project. |
|
|
Proof of concept for the new implementation of the Back office application. No longer used. |
|
|
Customer portal UI project. |
|
|
Collection of shell and SQL scripts for various database processes such as baselines, copy-downs, daily reports, etc. |
|
|
Remote deployment tool. |
|
|
Internal application used to track messages. It is mostly used with the deployment project and systems initiatives. |
|
|
Device mangement UI project. |
|
|
Source code for Touchscreen, Back Office, and Remote Connection Management applications. |
|
|
Configuration files used for building FullCount operating system images. |
|
|
Currently unused (October 2014). |
|
|
Obsolete. Custom Mandrill implementation which was needed to get TLS 1.2.0 support with Java 7. |
|
|
Source code for mobile applications (Android, iOS, etc.). |
|
|
API project for at-fullcount-model. |
|
|
Source code for FullCount-specific software packages installed on tablets, terminals and servers. |
|
|
Shared password databases for FullCount staff (internal use only). |
|
|
Electron application. Used to run our POS application. |
|
|
Repo to house shared/reusable logic between all our React applications |
|
|
Obsolete. Old device management UI project. |
|
|
Source code for customer self-service mode. |
|
|
Collection of shell scripts for various server processes such as remote connections, remote backup reports, etc. |
|
|
Obsolete. Most of the contents have been moved to the packages repository. |
|
|
Miscellaneous shared libraries and classes not tied to a specific database schema. |
Conventions
By convention, Subversion repositories usually contain the following directories:
This is a convention, not a requirement, so individual repositories may be organized differently.
branches
A directory in which to create various named branches of the main development line. Branches are often used for experimental features that are not yet ready to be included in trunk.
tags
A collection of tree snapshots that are created (and possibly, but less often, removed) and never changed. Tags are typically used to "mark" a collection of files that were used to build a specific version of an application or software package. For example, if a new build or release is created every month, you might create a new tag every month.
trunk
The directory under which the main project development occurs. This is usually the bleeding-edge version that is a work-in-progress.
References