Client Installation

PostLab Local is a special version of PostLab that only works with local GitLab servers.

Download

The latest PostLab Local release is available here under [Local].

Prerequisites

Before launching the PostLab Local client on your Mac...

1. Disable all unused network connections on your Mac.

   • Disable all active network connections except one to simplify administration.

2. Disable IPv6 on any enabled network connections.

3. Confirm your local area network has an active DHCP server in place.

4. Add your PostLab Local Server's IP Address and Hostname to the /etc/hosts file.

5. Add the Self-Signed Certificate to your Mac.

6. Log into PostLab Local server, then reset your password.

Add Your PostLab Local Server's IP Address and Hostname to /etc/hosts

1. In Terminal, open the /etc/hosts file in your favorite text editor. For example, here's how you would open /etc/hosts using the nano editor:

sudo nano /etc/hosts

1. Add a new dedicated line with the the IP address and hostname in the form of:

ip_address hostname

Example:

192.168.1.3 hoth.postlab.local

The /etc/hosts file must have only one entry for the Hostname. Even if another line with the same Hostname is commented out for testing purposes, doing so will interfere with the PostLab Local Client working as expected.

1. Save the /etc/hosts file.

2. Done!

Add the Self-Signed Certificate

For Team Leads: have you created the self-signed certificate for your Team yet? If you still need to, stop here, follow these steps to create a certificate on your PostLab Local Server, then continue.

1. Open your PostLab Local Server in a Web browser by its Hostname and Port 8443 (e.g. https://hoth.postlab.local:8443)

Are you getting a 502 error in your Web browser? GitLab's services are still starting up. Wait a few minutes, then retry accessing the PostLab Local Server in your browser.

1. Save the certificate to your local computer by dragging the certificate icon in your Web browser's address bar to a local folder.

2. In Finder, double-click the certificate file, which will launch Keychain Access.app.

3. When Keychain Access asks you where to store the certificate, choose System.

4. In Keychain Access, set Trust > When using this certificate: to Always Trust.

Can't see the PostLab Local Server certificate in Keychain Access? In Keychain Access.app, go to View > Show Expired Certificates. Although the certificate may be expired, as long as you downloaded it from the PostLab Local Server, it's still valid and trustworthy.

1. Done!

Log into PostLab Local server, then reset your password

1. Open your PostLab Local Server in a Web browser by its Hostname and Port 8443 (e.g. https://hoth.postlab.local:8443)

2. Sign in under that newly created user provided by your PostLab Local support team.

3. Once you sign in as the new user, you can either update the password or use the same password.

4. Done!

Now you're ready to launch the PostLab Local client.

Initial Use

When you first launch the PostLab Local client, it needs two pieces of information:

1. An Activation number, which is your license key.

2. Your PostLab Local Server's Hostname.

   • This is the same Hostname as your GitLab server. (Example: hoth.postlab.local)

The first time you activate the PostLab Local client, your computer needs access to the public Internet. If your network has restrictions in place, you may have to add this HostName and Port to any Allowed Lists: https://wyday.com on port 443

Activate PostLab with the provided license key.

Click + to add your GitLab server

Enter your GitLab server URL or IP address

Once you click Continue, PostLab Local is ready to use from this computer.

To get started, try one of our Initial Workflow Checklists for your NLE/video editing app of choice.