- Postlab Local requires GitLab EE 14 (all minors) or GitLab EE 15 up to 15.8.3. No other version is supported.
GitLab CE and EE are identical, but GitLab only offers (paid) support for EE. An unlicensed EE instance is the same as CE. However, migrating from CE to EE isn't easy so GitLab recommends installing EE anyway. If for some reason you'd require GitLab support, this way the option is at least on the table. In practice, no support or a license is needed to use GitLab with Postlab.
- Make sure your server accepts incoming connections on port
GitLab has two ways to manage settings, and those ways partially overlap. Hence, you'll configure some settings in the
gitlab.rbfile, and others through the management console ("website").
/etc/gitlab/gitlab.rb, you must issue a
gitlab-ctl reconfigurecommand for the new configuration to take effect.
Some server settings are only available to configure in
gitlab.rb. Required settings for Postlab Local are listed below.
This should be an
Please consider a good backup strategy that allows you to restore your server if needed. More direction is available in GitLab's documentation.
Disable emailing in GitLab:
Default project feature settings
This setting will enable/disable certain project features. Disable these settings, as they're unnecessary for Postlab use:
Default User Settings
In Postlab, a Team is a GitLab root-level group. Typically, users should not be able to create Teams. To disable this functionality:
It's a best practice to ensure your repositories/projects live on a different volume than your OS. More direction is available in GitLab's documentation.
You MUST enable LFS. Direction on enabling LFS is available in GitLab's documentation.
If you want to keep LFS storage locally, typically the syntax would look like this:
These settings are available inside the Admin pages of your GitLab server.
Visibility and access controls
Default project creation protection
Developers + Maintainers
Default project visibility
Default snippet visibility
Default group visibility
Restricted visibility levels
Private: disabled Internal: enabled Public: enabled
Enabled Git access protocols
Account and limit
New users set to external
Prompt users to upload SSH keys
Allow password authentication for the web interface
Enforce two-factor authentication
Initial default branch name
Initial default branch protection
Enable repository checks
Enable automatic repository housekeeping
Incremental repack period
Full repack period
Git GC period
Continuous Integration and Deployment
Default to Auto DevOps pipeline for all projects
Enable shared runners for new projects
Postlab Local requires a license key (or
activation number), and your license key is linked to a GitLab server. Before we can create a license key, you'll need to create an access token from your GitLab server, which you'll send to us.
- 1.Create a GitLab user expressly for creating the access token. This user does not have to be an admin.
- 2.Log in as that user.
You must log into GitLab’s web interface with this user at least once.
- 3.Go to
User Settings > Personal Access Tokens.
User Settings > Personal Access Tokens
- 4.Add a token, and give it a name in
- 5.Leave the
Expiration dateblank. Do not add an expiration date, as this token should never expire.
- 6.Enable the
read_apipermission and nothing more.
Before you click
Create personal access token, have your password manager ready or have something available to record your access token. Clicking
Create personal access tokendisplays the access token only once.
Create personal access tokenthen record the access token displayed in a safe place, like a password manager.
Once we receive your access token, we'll process it, then send you your
activation number, which is your license key for the Postlab Local client.
Next, you can start creating users and groups.
Postlab Local only supports local GitLab users. Some GitLab features like LDAP or OmniAuth are currently unsupported in Postlab Local.
Root-level groups in GitLab are displayed as Teams in Postlab. Also, users can belong to multiple Teams/groups.
Postlab Local does not support GitLab subgroup or project user permissions, and using these will break Postlab.
A user can either be a
Maintainerscan create Folders,
Productionsand add FCP Libraries and Premiere Pro Projects, but aren't allowed to delete
Maintainerin GitLab is called an
Ownerscan delete Folders,
Productions, FCP Libraries, and Premiere Pro Projects. You can also grant
Ownerspermission to create and remove Folders within a Team. You can set this up in
Settings > Generalof a group.
Guesthas read-only access.
Setting a user's
Max rolein GitLab to anything other than
Ownerwill result in a Team Member being assigned a
Guestrole in Postlab.
Once you create a user, you (or the new user) must take these steps before using the PostLab Local Client:
- 1.Log into the GitLab server via a Web browser as that user.
- 2.Reset the password for that user.