Setting up your own GitLab server really is much easier than you might think.
Below are all the steps needed for you to get started.
Install and setup a server
You’ll need to install an Operation System on your server. We recommend you use a Virtual Machine for this on a hypervisor like VM Ware or Hyper-V.
You’ll need to install a Linux distribution of your choice. We recommend that you use CentOS 7. It’s a free and very stable distribution. You can download it here.
After you’ve setup your server to your liking you can install GitLab. To do that follow the guide here.
With this you’re installing what GitLab calls an Omnibus package. That meanse that GitLab installs everything at once, and maintains it after that. All you have to now is configure GitLab.
Configuring GitLab Server
We recommend you configure the following things:
- Configure the URL for GitLab
- Enable HTTPS
This is optional but then again it isn’t. Security is important. Just do this.
- Store the data on another disk instead of the start up disk
- Configure Active Directory / LDAP
This is optional off course but if you have any it’s much better to go this way.
- Configure your Backups
- Configure Git LFS
You’ll need to enable this and setup a location where this is stored. These are normally large files. So make sure your storage is large and fast.
Also learn how to update GitLab by reading this. It’s really easy.
Configuring GitLab Application
Some options must be set in the GitLab web application. Here are some recommended settings for you to consider. All these options are in your admin area in the settings tab.
In our situation we want the users only to see the groups and projects they have access to. GitLab has an option that users can see other projects and groups and request access to them. Most of our editors would find this confusing and also we’d like to be in charge of who sees what.
- Default branch protection to Partially protected
- Default project visibility to Private
- Default group visibility to Private
- Restricted visibility levels to Private disabled, Internal enabled, Public enabled
And since we’re talking about access rights have a look at this post as well: Allowing people to create groups
A GitLab server configures for PostLab doesn’t need any import sources so you can disable all of these.
A GitLab server configured for PostLab only uses HTTPS and not SSH for project.
In the admin area / Settings go to the Enable Git Access Protocols and set this to Only HTTP(S).
Default Project Limit
This option means that users are not allowed to create more projects than this number. Set this number to whatever you need it to be.
Also take a look at the Appearance tab in the admin area. Here you can customize GitLab even further.
These are our recommend settings. Take a look at all the setting to get more familiar with GitLab and all the options you have.
When you’re here you’ve got yourself a working server. Start configuring PostLab and work with Final Cut Pro like never before. If you still got questions drop them in our forum here.