The process for serving a team's VI Package Repository over HTTPS looks like the following:
- Create and manage a repository locally (using VIPM Pro's Repository Manager)
- Deploy the repository files to a web server (using some sort of upload/deployment tools)
- Manage client access/security
- Connect clients to repository
Note: It may be easier/preferable to host your repository on a network file share, such as \\servername\share\vipm-repository\ and simply use Windows File Permissions to manage access to the files. Then, you can manage the repository in place, without (A) having to upload/sync it to a web server and then managing user authentication.
Create and Manage a Repository Locally
You will need to use VIPM Pro to create and manage a repository on your local file system.
Deploy Local Repository files to a Web Server
You will need to deploy/upload/sync your local repository files to a web server, so that it can be served to users over HTTPS. There are a variety of tools and mechanisms to do this.
For example, if you are using VIPM Pro to manage a local repository located at C:\Data\MyLocalRepository, you would need to sync/upload that folder to web server at https://mydomain.com/packages/ (or similar). You might do this with SFTP, WebDAV, AWS CLI, or some other file transfer tool.
Manage Client Access/Security
You should secure your web server by requiring an HTTPS connection. This will help ensure that packages are protected, as well as any usernames and passwords transmitted.
You should implement some sort of Basic Authentication scheme, which will cause the web server to request a username and password. There are a variety of tools to achieve this.
Article is closed for comments.