OAuth for user integration
GitLab provides OAuth for an easy user integration. Just go to your GitLab app in the NWS Customer Interface and click on "Settings". You can drop your OAuth credentials to use the pre-configured providers (GitHub, Twitter, Goolge, Facebook, GitLab.com, BitBucket, AzureAD, ADFS) at "External authentication with OAuth".
Just go to your GitLab app in the NWS Customer Interface and click on "Settings". Scrawl down to "Update GitLab Runner" and push the button.
Remaining storage volume
Just go to your GitLab app in the NWS Customer Interface and click on "Usage".
Upgrade to a bigger plan
Just go to your GitLab app in the NWS Customer Interface and click on "Manage contract". Here you can upgrade to Advanced or Premium plan. If the Premium plan is no longer sufficient, contact us via firstname.lastname@example.org and we will provide you with a customized solution on OpenStack.
Access via SSH is not possible with the GitLab SaaS app.
You can only access your GitLab via https.
But you can use Git's credential.helper for effortless access. Just set this up once and you won't have to enter your credentials (username + PW) every time. You can do your Git pulls and Git pushes comfortably that way.
If access via SSH is essential for you, we can set up a custom GitLab instance on our OpenStack.
Here, the resources (CPU, RAM, storage) can be freely determined and adapted at any time.
Features that are not possible in our standardized SaaS app can also be implemented here (e.g. access via SSH, GitLab pages, self-selected update period, freely selectable backup cycle).
There is no contract period and billing is based on the resources used and the support time provided (which is accounted for separately in contrast to our SaaS offer). Just write us here, if this sounds interesting for you.