auth to gitlab at non-root path

[hisnamewasjaan]

When using glab auth login, I am prompted for a hostname. But how do I specify an additional path?
My customers gitlab is at rep.company.dk/git

[profclems]

Wow... I never expected an instance to have be hosted with a hostname/path url.

This will be creating a lot of issues when used with glab especially when fetching the project name from the git url. glab assumes that if the url is [email protected]:path1/path2.git or https://gitlab.companyname.com/path1/path2, the project path is path1/path2.

Maybe we may have to consider this as an issue and see ways we can fix it. But it is advisable to use a subdomain for a GitLab self-hosted instance.

[hisnamewasjaan]

hmm, well git remote -v reveals [email protected]:group/project.git as stated earlier.
So ssh, right?

[hisnamewasjaan]

@profclems , any further insights on this? Or what I am missing?

[zemzale]

Can you maybe share your glab config, of course by removing all the sensitive stuff. Maybe it just fails because the config somehow is wrong.

[hisnamewasjaan]

Naturally...

$ cat config.yml 
# What protocol to use when performing git operations. Supported values: ssh, https
git_protocol: ssh
# What editor glab should run when creating issues, merge requests, etc.  This is a global config that cannot be overridden by hostname.
editor:
# What browser glab should run when opening links. This is a global config that cannot be overridden by hostname.
browser:
# Set your desired markdown renderer style. Available options are [dark, light, notty] or set a custom style. Refer to https://github.com/charmbracelet/glamour#styles
glamour_style: dark
# Allow glab to automatically check for updates and notify you when there are new updates
check_update: false
# configuration specific for gitlab instances
hosts:
    gitlab.com:
        # What protocol to use to access the api endpoint. Supported values: http, https
        api_protocol: https
        # Configure host for api endpoint, defaults to the host itself
        api_host: gitlab.com
        # Your GitLab access token. Get an access token at https://gitlab.com/profile/personal_access_tokens
        token:
    rep.company.dk:
        git_protocol: ssh
        token: 8YgXXXXXXXYBHXnxrs
        api_host: rep.company.dk/git

Thank you for taking a look :)

[zemzale]

Well the config looks fine. Nothing pointing that something might be wrong.

I am actually real puzzled, why it doesn't work.

Could you try then a simple curl request and see if that works? Maybe there is some other weird reason why it doesn't work.

curl --request GET 'https://rep.company.dk/git/api/v4/projects/<id-of-project>/merge_requests' \
     --header 'Authorization: Bearer <your-token-here>'