DigiVC documentation

01

DigiVC documentation

A practical guide to installing, administering and using DigiVC.

→ 02

What DigiVC is

DigiVC stores file content and history on a central server. A user sees normal folders and files in a local **workspace**, while the server keeps the authoritative version, revisions, permissions, locks and audit trail.

→ 03

Installation and initial setup

The production server is intended for Oracle Linux 9 or DigiOS. PostgreSQL must be version 16 or later. The database may be local or hosted on a separate PostgreSQL server.

→ 04

Login, navigation and roles

Open the DigiVC public URL and enter your username and password. If an administrator created the account with a temporary password, WEB/Admin may require an immediate password change.

→ 05

Projects and repositories

Open **Projects → New project** and enter:

→ 06

Desktop Client and workspaces

The Desktop Client is the primary interface for daily file work.

→ 07

Command-line transfer client

The public CLI is intentionally limited to two operations:

→ 08

Users, groups and permissions

This section is intended for system administrators and project/repository owners with the required permissions.

→ 09

Revisions, locks, checks and conflicts

Every successful commit creates a new immutable revision. History shows:

→ 10

Import and migration

Import reads content from Git, GitHub, GitLab or SVN and converts it into a DigiVC repository. Git/SVN are not the DigiVC engine; they are migration source connectors.

→ 11

Reports, backup, audit and operations

In **Reports** select:

→ 12

Practical workflows

Goal: the team develops an internal “Claims Portal” system.

→ 13

Troubleshooting

Cause: the PostgreSQL client package is not installed.

→ 14

Glossary

**Access request** — a request from a user for project or repository access.

→