Parent page: Altium NEXUS Server
The Altium NEXUS Server installation provides localized (and centralized) version control, courtesy of its Version Control service. This service provides version control possibilities right there where you need them, locally, without searching, or paying for, external VCS management software.
By defining design repositories in this centralized fashion, an organization can fully control which repositories its designers can access and use.
There are two key advantages to using this centralized Version Control service:
- You have common users and rights management for both the Altium NEXUS Server and SVN. When you sign in to the Altium NEXUS Server, the Version Control service works with your session/credentials.
- Repositories defined through the Altium NEXUS Server (through the VCS page (Admin – VCS) of the NEXUS Server's browser-based interface) are populated to the design client automatically during login, so users do not have to worry about URLs, protocols, password etc. It is simply configured once, on the server, and shared with the intended users as required.
Repositories can be created through the local Version Control service (SVN-only), or external repositories can be connected to (SVN or Git). Together, all repositories are centrally managed through the VCS page (Admin – VCS) of the NEXUS Server's browser-based interface, in terms of:
- Their displayed name, description and repository path.
- Their configured accessibility – which specific users can access them (or roles in the case of repositories defined through the local Version Control service).
- Their availability – add or remove them centrally, rather than individual designers having to create and connect to repositories independently.
When an Altium design software user signs in to the Altium NEXUS Server, the Design Repositories available to them will automatically be added to the Data Management – Design Repositories page of the Preferences dialog. Note that the list will also include any 'unmanaged' repositories that have been manually added from this Preferences page.
Centrally define access to your organization's Design Repositories. Repositories can be internal to the Altium NEXUS Server installation, defined using the local Version Control service, or external through use of Altium NEXUS's built-in SVN, or third party SVN or Git service. Access control is performed through the VCS page of the Altium NEXUS Server's browser-based interface. When a user signs in to the Altium NEXUS Server, the Design Repositories available to them will automatically be added to the Data Management – Design Repositories page of the Preferences dialog.
Adding a Repository
To add a Design Repository, click the button, located at the top-right of the page. The Add Repository window will appear, use this to define the repository.
The properties required depend on whether you are creating a new repository using the local Version Control service, or linking to an existing, external repository:
- New – simply give the repository a name and a description.
- Existing – in addition to a name and description, you need to supply the URL to the repository, and valid credentials (User Name, Password) to access that repository (if required).
Create a new SVN-based Design Repository through the NEXUS Server's local Version Control service, or link to an existing repository (SVN or Git) that has been created external to the NEXUS Server.
A linked, external Design Repository is distinguished in the list of repositories by its External property being ticked ().
To edit the properties of a Design Repository at a later stage, click its associated Edit control (). To remove a Design Repository, click its associated Remove control ().
Sharing a Repository
Having centralized your Design Repositories, you need to ensure that those requiring access to a given repository – including the designers who will be working on board designs – have that access. This is achieved by sharing that repository, or rather managing its access permissions. To do this, click on the repository's associated Share control ().
The Manage Permissions window will appear, with all the controls necessary to share the repository with other users.
With Design Repositories centrally organized, sharing with others is simply a case of managing each repository's permissions.
Things to be aware of:
- For a local repository created through the NEXUS Server's Version Control service (i.e. not external), its default permissions share that repository with the user who created the repository, and the Administrators role. Both of these have full Read/Write access.
- For an external repository, it is shared with no-one by default – not even the user who added a connection to it through the interface.
- Only local repositories (not external) can be shared with defined role groups for the NEXUS Server, or publicly. Roles are listed after individual users.
- In terms of permissions, a user/role has Read/Write access when the Can Write option is enabled (). If this option is disabled, they have Read access only.
- To remove an existing user/role from having shared access to a repository, click the associated Remove control ().
External Access to a Local SVN Design Repository
A Design Repository that is created through the NEXUS Server's local Version Control Service can be accessed using an SVN client such as TortoiseSVN. Access is made using the regular network protocol (the svn:// is currently supported). The correct repository address can be accessed/copied from two places:
- The VCS page of the NEXUS Server's browser interface – within the Repository Path field for the target repository.
An 'internal' repository created from the NEXUS Server will show its address path relative to the server, which is the
localhost address of the host PC.
From the perspective of a NEXUS design client – or any application not on the server host PC – the repository address paths are based on the name their host PCs.
Use the acquired address in your Subversion client's repository browsing facility. On first access an intermediate Authentication dialog will open requesting valid connection credentials. Enter the name and password of a NEXUS Server user account to proceed. These credentials are valid if:
- The user account was added after the repository was created in the NEXUS Server. The users that apply to created repositories can be seen in the
passwd file found in the server PC's
\ProgramData\Altium\NexusServerData\Repository folder – see below.
- The repository has been shared with the user account, by adding that username via the Add User command in the server's Manage Permissions for <repository name> window. This is evident in the repository's
authz file, found in the server PC's
Browsing the content of a Design Repository created through the Altium NEXUS Server installation's local SVN-based Version Control service.
Server & VCS User Synchronization
When a new user for the Altium NEXUS Server is created, the defined credentials (User Name and Password) for that user are stored in both the server's database and the Version Control service, since the latter cannot access the password from the former directly. The password is stored with the Version Control service in plain text format (in the \ProgramData\Altium\NexusServerData\Repository\passwd file).
The entries in this list provide access to the NEXUS Server SVN repository when working with the service through the NEXUS design client. There may be occasions where a user's credentials are not included in the file, such as when NEXUS Server users already exist when the first SVN repository is created (rather than the other way around). This can be addressed by manually adding those name/password combinations to the
passwd file, or by re-entering the password for each user profile in the NEXUS Server – the latter approach will populate the
passwd file accordingly, and without requiring direct access to the server PC.
In a default installation of the NEXUS Server, user credentials are stored for the Version Control service in the associated Passwd file.
Deleting a Repository
To delete a repository from the NEXUS Server's Version Control service, click the Remove control () associated with that repository, on the VCS page of the NEXUS Server's browser-based interface.
External repository entries can be deleted, irrespective of whether or not the repository contains any projects. Local repositories on the other hand (those created internally through the NEXUS Server's Version Control service) can not be deleted if they contain one or more projects. You will be alerted to this, and should remove the projects first before being able to proceed with the deletion.
Even then, if a local repository has no projects, it will not actually be deleted, but rather moved to an archive directory (\ProgramData\Altium\NexusServerData\RepositoryDumps, for a default NEXUS Server installation). The repository will be contained within a Dump file, with a Unique ID prefix (e.g. 775f6c22-b9a1-468c-9f1f-4f217bb3be6b_central design repository.dump).