Provide ability to set repository path & use human-readable names for repository folder name about scm-manager

[JustAnotherRandomUsername]

Hello vrreg!

(IMHO) You must not be rename UNIQUE path repository generated by scm-server!

1. This feature (work logic) is allows to change name of your repository and guarantees that the path to files never lost.

2. If you need any integrations, connectors or some custom query to scm-server please use scm-server api

example script:

#!/bin/bash

#scmadmin access token can be generated in gui
token="eyJhcGlLZXlJZCI6IjM2VGdXZDZJYUciLCJ1c2VyIjoic2NtPEQtaW4iLCJwYXNzcGhyYXNlIjoiaDhJZUNsSnBUZ0IKSDRTRzNzM2YifQ"

#text file to store info
vfile="finded_full.txt"

#clean old file
rm -rf $vfile

#create list uid+name by list uids
for repouid in $(ls -1 /data/repositories)
do
v=$(curl -s -X 'GET' "http://127.0.0.1/api/v2/legacy/repository/$repouid" -H "accept: application/json" -H "Cookie: X-Bearer-Token=$token")
reponame=`echo $v | awk -F'"' '{print $4}'`
echo $repouid $reponame >> $vfile
done
echo "data saved to path: $vfile"

---

Best regards

[vrreg]

Thanks for your comment. My comment above was an example. One can leave the UNIQUE ID but simply re-name the directory and update the repository-paths.xml

ie.
<?xml version="1.0" encoding="UTF-8"?> <repositories creation-time="1691612257430" last-modified="1691620475246"> <repository id="4OTmTj7Ma7">repositories/MYCOOLREPOSITORY</repository> </repositories>

[eheimbuch]

Hey @vrreg,

would it be sufficient if we create another directory containing sym-links to all repositories? Each sym-link could be named as your actual repository name. We have already discussed this "feature" internally some time ago.

Your proposal could work but we had to verify that none of our many plugins breaks with this changes. Also, this will most likely bring complicated edge cases like path conflicts and validations.

[vrreg]

Hi @eheimbuch ,

Thanks for considering my suggestion.

I would say this might become convoluted in the long run and a challenge to maintain.

Right now to backup and SCM setup, one could copy the .xml configuration files (in addition to saving the repository data) . With a folder of symlinks, that's one more thing that must be properly saved and backing up symlinks can be tricky.

[pfeuffer]

Hey @vrreg ,

sorry for the late follow-up. You can install the custom storage plugin (maybe you have found it already in the meantime). Here you can see and modify the paths for all repositories and also configure a custom path pattern for new repositories. This should fit your needs. If not, please let us know.

Regards
René