Besides using Postlab as a cloud service for remote collaboration, you can also use Postlab on-premise — perfect for air-gapped productions and organizations that want to keep everything in-house. Postlab Local allows for studios and facilities to roll out Postlab in-house, thus eliminating the need for a rigid security vetting process by IT/InfoSec.
Postlab Local is a macOS client that is adapted to work solely with a vanilla off-the-shelf installation of either Gitlab EE 14 or 15.
Postlab Local does not support non-local area networks. Postlab Local can access your local GitLab server deployment remotely via a VPN, but you're not able (nor allowed) to use Postlab Local with cloud-based GitLab instances.
The central part of Postlab Local is your GitLab server. There are multiple ways to run a server; pick the one that suits you best.
Note: we do not offer support for installing GitLab. If you're pursuing Postlab Local, you (or someone on your team) should have the server admin chops needed to install, deploy, and maintain GitLab.
Jellyfish comes with Postlab Server pre-installed and integrated with Jellyfish user management. If you have a Jellyfish, send us the token exposed in the Jellyfish Manager on the Postlab page.
If you're on bare metal or using a NAS, you know what you're doing. If you're in doubt, this is not for you - hire someone to manage your GitLab.
Installing GitLab on macOS is only possible through a VM. We’ve seen good results installing Ubuntu on a VM using Parallels.
- Is the IP address for the server static? (It should be.)
- Will the clients connect to an IP address or DNS name? If the latter, set up a hostname for the server.
- Do you need multiple teams or just one? Each GitLab group shows up as a team in the Postlab Local client.
- Have you devised a backup strategy? How often should GitLab perform a backup? To which volume should GitLab back up?
Read up on all the details about getting Postlab Local to work on Gitlab: