Gitlab documentation, configuration

Technology Infrastructure and Services
1

Where can I see gitlab configuration? and history of values? I don’t see where to find in e.g. mfmt / Seed · GitLab

Gerrit (mostly I know the Wikimedia instance) maintains a lot of configuration in internal (but some (all?) are publicly accessible) git repos. So I was wondering if gitlab had anything similar. I haven’t been able to find it yet.

Also looking for a repo for Ssh · User · Help · GitLab I have edits to make to the docs.

e.g. key types that are supported upstream but not here. this instance is running a too old SSH for FIDO2 resident SSH keys. the docs say I can use them and the settings interface lets me upload them. but then they don’t work.

2

Hi @electricat , the Git Lab configuration is here: roles/gitlab · master · mfmt / Seed · GitLab

We keep our ansible inventory in a private git repo because it contains IP ranges and other sensitive information, but all of our ansible roles are public, which should provide a reasonable sense of how things are configured.

The Ssh User file you reference is maintained by Gitlab, not us. It ships with the version we are using.

3

Also - can you say more about how you’d like to help? At the moment, we can really use support expanding the documentation on help.mayfirst.org more than anything. The main file on helping with documentation is here: How to contribute to documentation | Help

And, we have a number of bracketed empty links on the “common tasks” page under the Control Panel. If you can take a crack at one of those pages it would be great. I’d be happy to provide feedback.

4

I figured there must be a way to customize it locally. If you don’t know how I could investigate that at some point.

but the configuration part holds: how do you set which key types are permitted? are changes logged somewhere a la those git repos I was talking about for gerrit? see e.g. Log - refs/meta/config - mediawiki - Gitiles and Log - refs/meta/config - mediawiki - Gitiles

at any we should disallow key types which won’t work because that host has a too old SSH. (disallow the FIDO2/_SK types)

for future reference where is the right bug tracker to report stuff like that? I figured gitlab issues on a gitlab project for configuring our gitlab itself. but I couldn’t find such a project.

I don’t remember exactly what I wanted to edit. I could take a crack at some new pages but I guess initially was thinking about fixing stuff that I saw was wrong/incomplete.

5

I suspect the proper fix is to upgrade the virtual guest running gitlab and upgrade gitlab itself. This isn’t a high priority for us at the moment. We intentionally setup this gitlab instance specifically for May First staff - not as a repo for members to use for themselves because we knew we didn’t have the time to maintain it properly for general use.

It’s for reasons like this that I wanted to check in on what you have in mind. I wouldn’t want you to spend a lot of time on something that isn’t a priority for us and would just languish.

At the moment - the best place to report problems is via our support system - email support@mayfirst.org. Because many of the infrastructure bugs have security implications, we don’t have a public issue tracker for them - we keep that locked down.

6

sure, but in the meantime would be good to disable types that won’t work.