But still, everyone who gets in contact with the server will get an autocreated useraccount. This will let you define a superuser for your perforce server. Within your server package comes a little tool called p4 that will let you make changes to your server.
But do not be afraid, this can easily be changed.
The first thing to mention is: At this point, the perforce server is completely unprotected! Whoever connects to the server and tries to execute a command can do it and the first user to try might even become a perforce super user with the right to change the server settings.
But i recommend you take a longer look at the documentation to see what they have to say about production installation. Yes, this is a basic installation and it can be done in a few minutes.
On the download page, choose the right package for your distribution and architecture. Just replace perforcePath with the directory you used. This is the bash syntax to tell your server where it can find perforce and on which port it runs. Just pay attention to the disk space available, there should be plenty for your projects to come! Make a directory where perforce can live.Decide which user will run the perforce server.Please avoid running it as root!Ĭondensed to the bare minimum these are the steps to get a Perforce Helix Server up and running in literally minutes:
If you are doing a production installation, you might want to put in a little more thought about where and on which user you install perforce. Basically a production installation is the same as their „10 minute test drive“ installation. Getting it running was actually impressively simple. Oh, and please be aware: I am not an expert on perforce! Server sideīasically you have two options: Use a perforce cloud service or install it on your own server. I have to admit, the part of it being free for small teams was a huge plus.
So we did not use the pro integration either.) (Spoiler: The plugin did not work for us and we wanted to use it on our personal projects, too.