villaeg.blogg.se - Perforce helix server setup

Perforce helix server setup how to#

Click on Inbound security rules on the left.

Navigate to the newly created Resource Group.

All the input fields on the other blades can be left to their defaultsĪfter the Virtual Machine has been created, we can open the port to allow users to connect to the Proxy.

In the Networking blade, it is important to create a Virtual Network that does not have a conflicting address space with the Helix Core Virtual Network.

Choose the size you need for your cache.

At the Disks blade, we’ll add a disk where the cached content can be placed upon.Other distributions can be chosen as well, but here we choose CentOS to keep the proxy the same as the Enhanced Studio Pack.

For Image, select CentOS-based 7.9 - Gen2.Choose the correct Region you want the proxy to be deployed to.In the Virtual machines page, select Create -> Virtual machine at the top left.Under Servers, select Virtual Machines.Type virtual machines in the search box.Follow these instructions to set up the Virtual Machine: For this example, we’ll use a Standard D2s v4. The machine’s specifications can be lower than the commit server. It contains Helix Core, Swarm, Hansoft and a Windows workstation, with 5 licenses to go with that.

For this guide we have installed Helix Core through Perforce’s Enhanced Studio Pack in the Azure Marketplace. To use the Perforce Proxy, a Helix Core commit server needs to be available. The Perforce Proxy can be used for on premises deployments of the Helix Core commit server, or Azure deployed Helix Core commit servers. A scenario where a Perforce Proxy is beneficial is to bring Perforce closer to its users, whether that is for working from home scenarios or teams that span the globe.

Perforce helix server setup how to#

In this guide we’ll show how to set up a Perforce Proxy in Azure.