Server Configuration
Requirements
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
8443
.
GitLab
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").
gitlab.rb
File Location: /etc/gitlab/gitlab.rb
After modifying /etc/gitlab/gitlab.rb
, you must issue a gitlab-ctl reconfigure
command 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.
Website settings
These settings are available inside the Admin pages of your GitLab server.
General
Visibility and access controls
Account and limit
Sign-in restrictions
Repository
Default branch
Repository maintenance
CI/CD
Continuous Integration and Deployment
Access Token
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.
Create a GitLab user expressly for creating the access token. This user does not have to be an admin.
Log in as that user.
You must log into GitLab’s web interface with this user at least once.
Go to
User Settings > Personal Access Tokens.
Add a token, and give it a name in
Token name
.Leave the
Expiration date
blank. Do not add an expiration date, as this token should never expire.Enable the
read_api
permission 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 token
displays the access token only once.
Click
Create personal access token
then record the access token displayed in a safe place, like a password manager.Send us your access token: postlab@hedge.video.
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.
Users & Groups
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.
Groups
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.
Users
A user can either be a Maintainer
, Owner
, or Guest
.
Maintainers
can create Folders, Productions
and add FCP Libraries and Premiere Pro Projects, but aren't allowed to delete Productions
.
A Maintainer
in GitLab is called an Editor
in PostLab.
Owners
can delete Folders, Productions
, FCP Libraries, and Premiere Pro Projects. You can also grant Owners
permission to create and remove Folders within a Team. You can set this up in Settings > General
of a group.
A Guest
has read-only access.
Setting a user's Max role
in GitLab to anything other than Maintainer
or Owner
will result in a Team Member being assigned a Guest
role in PostLab.
Once you create a user, you (or the new user) must take these steps before using the PostLab Local Client:
Log into the GitLab server via a Web browser as that user.
Reset the password for that user.
Last updated