What DigiVC is

Core idea

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.

The usual workflow is:

Select repository → Checkout → Work locally → Status/Diff → Update → Commit

Core objects

• Project — an organizational container, for example “ERP Platform”.
• Repository — a versioned store inside the project, for example “Server”, “Client” or “Documentation”.
• Workspace — a local working directory connected to a repository.
• Revision — an immutable record of one accepted change.
• Repository address — the permanent address used by clients to locate a repository.
• Vault Storage — the protected internal content store.

Example repository address:

digivc://digivc.company.example/ERP/Server

What DigiVC is not

DigiVC is not merely a web interface over Git or SVN. Normal DigiVC revisions, permissions, audit and Vault Storage are native DigiVC functions. Git and SVN are optional import and migration sources only.

History and protection

A successful commit creates a new revision. An older revision is not modified. This makes it possible to:

• see who changed what, when and why;
• compare versions;
• provide evidence during an audit;
• restore the correct content;
• prevent silent history rewriting.

Which interface should I use?

WEB/Admin — when creating or managing system objects.

Desktop Client — for normal daily file work.

CLI transfer client — when a script or terminal operation only needs download or upload.