Hi
It is that time of the year when there is some time to do some hacking.
Looking at the CLNET repositories I manage, I noticed two things. The first one is that there may be a GitLab limit on the number of repositories that one can have under her/his name. The second is that I have several "legacy" repositories with their own "group" and some newer ones without. (Plus there is the issue of separate repositories for documentation, but I can live with that).
Please bear with me. I am not a GitLab expert and I am not running the show.
I would like to know how we could go ahead and make it possible to "consolidate" "projects" and "repositories" in CLNET GitLab.
The idea would be to have something similar to Github "organizations".
Is this something that you think could benefit CLNET?
All the best
Happy New Year
Hi Marco,
It is that time of the year when there is some time to do some hacking.
Looking at the CLNET repositories I manage, I noticed two things.
The first one is that there may be a GitLab limit on the number of repositories that one can have under her/his name.
That's correct, but the admins can help you raise the limit, if you need, or create new groups (which don't have this limit).
The second is that I have several "legacy" repositories with their own "group" and some newer ones without. (Plus there is the issue of separate repositories for documentation, but I can live with that).
Yes. That's how I set up GitLab when we set it up: in the "old days" there were directories per project. Some directories had one repository, some had multiple. The structure in GitLab that allowed the same setup was to create a group per project and import the repositories from the on-disk project directory. There's another reason to set it up this way: all repositories need to be allocated to either a user or a group. This actually maps nicely from GitHub as well, I think, which has the option to create organizations (groups) or user accounts; either can have repositories.
Since the original setup of our GitLab instance, GitLab has added the concept of "nested groups": groups-in-a-group. I've never seriously considered it for anything, but it's a functionality that we have available if we want it.
Please bear with me. I am not a GitLab expert and I am not running the show.
No problem! Happy to be challenged or simply requested for an explanation. If there's a better way, I'm all for it!
I would like to know how we could go ahead and make it possible to "consolidate" "projects" and "repositories" in CLNET GitLab.
Could you explain a bit what you're looking to achieve? I'm not sure what the result looks like when "projects and repositories" are consolidated.
The idea would be to have something similar to Github "organizations".
Sure. I *think* I set it up that way, using groups. Does the explanation concerning my reasoning help your thoughts?
Is this something that you think could benefit CLNET?
Regards,
Thank you Erik,
(sorry for the delayed answer; family got in the way after all).
I guess my next question is whether you can have "hierarchical" groups. Apart from that, I will bug you separately to rearrange my repositories.
All the best
Marco
On Thu, Dec 30, 2021 at 10:05 PM Erik Huelsmann ehuels@gmail.com wrote:
Hi Marco,
It is that time of the year when there is some time to do some hacking.
Looking at the CLNET repositories I manage, I noticed two things.
The first one is that there may be a GitLab limit on the number of
repositories that one can have under her/his name.
That's correct, but the admins can help you raise the limit, if you need, or create new groups (which don't have this limit).
The second is that I have several "legacy" repositories with their own
"group" and some newer ones without. (Plus there is the issue of separate repositories for documentation, but I can live with that).
Yes. That's how I set up GitLab when we set it up: in the "old days" there were directories per project. Some directories had one repository, some had multiple. The structure in GitLab that allowed the same setup was to create a group per project and import the repositories from the on-disk project directory. There's another reason to set it up this way: all repositories need to be allocated to either a user or a group. This actually maps nicely from GitHub as well, I think, which has the option to create organizations (groups) or user accounts; either can have repositories.
Since the original setup of our GitLab instance, GitLab has added the concept of "nested groups": groups-in-a-group. I've never seriously considered it for anything, but it's a functionality that we have available if we want it.
Please bear with me. I am not a GitLab expert and I am not running the
show.
No problem! Happy to be challenged or simply requested for an explanation. If there's a better way, I'm all for it!
I would like to know how we could go ahead and make it possible to
"consolidate" "projects" and "repositories" in CLNET GitLab.
Could you explain a bit what you're looking to achieve? I'm not sure what the result looks like when "projects and repositories" are consolidated.
The idea would be to have something similar to Github "organizations".
Sure. I *think* I set it up that way, using groups. Does the explanation concerning my reasoning help your thoughts?
Is this something that you think could benefit CLNET?
Regards,
-- Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
Hi Marco,
On Sun, Jan 2, 2022 at 5:45 PM Marco Antoniotti marco.antoniotti@unimib.it wrote:
I guess my next question is whether you can have "hierarchical" groups. Apart from that, I will bug you separately to rearrange my repositories.
Yes, I see no problem with you using hierarchical or nested groups. There's one thing to mention though: managing project's websites from their GitLab repositories only works with specific repository and group name combinations: "<group>/<group>-site" (where that's "<group>/<repository>").
Regards,
Thanks! I guess that answers it.
It looks like one first needs some planning about the group/repos structure.
All the best
Marco
PS I have another problem: I changed my phone, but not my SIM card. My new phone is a dual-SIM one. I do not get the Google Authenticator code on my new phone. I was able to log in using one of the recovery codes but I do not see any way to migrate the 2FA, apart from disabling and resetting. Is that so?
On Sun, Jan 2, 2022 at 10:10 PM Erik Huelsmann ehuels@gmail.com wrote:
Hi Marco,
On Sun, Jan 2, 2022 at 5:45 PM Marco Antoniotti marco.antoniotti@unimib.it wrote:
I guess my next question is whether you can have "hierarchical" groups.
Apart from that, I will bug you separately to rearrange my repositories.
Yes, I see no problem with you using hierarchical or nested groups. There's one thing to mention though: managing project's websites from their GitLab repositories only works with specific repository and group name combinations: "<group>/<group>-site" (where that's "<group>/<repository>").
Regards,
-- Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
On Sun, Jan 2, 2022 at 11:23 PM Marco Antoniotti marco.antoniotti@unimib.it wrote:
PS I have another problem: I changed my phone, but not my SIM card. My new phone is a dual-SIM one. I do not get the Google Authenticator code on my new phone. I was able to log in using one of the recovery codes but I do not see any way to migrate the 2FA, apart from disabling and resetting. Is that so?
Go to the app on your old phone (no SIM needed I think). From the menu, select "Transfer Accounts" and follow the easy directions.
I would also consider getting a security key (like Yubico or Google Titan). I use my security key as the primary way, and the authenticator app when I don't have my key with me. You can have a key for each computer if you like. That's we we did at work.
On Sun, Jan 2, 2022 at 10:10 PM Erik Huelsmann ehuels@gmail.com wrote:
Hi Marco,
On Sun, Jan 2, 2022 at 5:45 PM Marco Antoniotti marco.antoniotti@unimib.it wrote:
I guess my next question is whether you can have "hierarchical"
groups. Apart from that, I will bug you separately to rearrange my repositories.
Yes, I see no problem with you using hierarchical or nested groups. There's one thing to mention though: managing project's websites from their GitLab repositories only works with specific repository and group name combinations: "<group>/<group>-site" (where that's "<group>/<repository>").
Regards,
-- Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
-- Marco Antoniotti, Professor tel. +39 - 02 64 48 79 01 DISCo, Università Milano Bicocca U14 2043 http://dcb.disco.unimib.it Viale Sarca 336 I-20126 Milan (MI) ITALY
-
Erik Huelsmann -
Marco Antoniotti -
Raymond Toy