PedyMaster's picture

Hi, Iam new here in forum, even though Iam using TKL for a while.

My question regards gitlab - I would like to have the git repo on my NAS so when my server dies and I lose the vmware with gitlub, I can still deployed new vmware and continue with work.

I notices that repos are in /home/git/repositories - I mounted NAS and tried to change the repo path in several configuration files to my NAS location but it did not work - when I tried to create new user it said "We are sorry, but something went wrong"

Then I tried to mount my NAS directly to /home/git/repositories but the same problem occured.

Is there a way of how to do this? Thanks for help in advance!


Note: I know that this should back up only repo and that there is a database too. I can backup database to NAS without problem. It is just the repo I dont know what to do with

Jeremy Davis's picture

Even though this is a TKL appliance the upstream software developers (and the community that supports them) are probably best placed to answer your specific questions. If they provide an answer perhaps you can post back...

In the meantime I suspect that it is a permissions issue (I guess you are mounting your external file system with root and GitLab uses a limted user account). Maybe you can use FUSE to mount your NAS with the GitLab user to acheive your desired results?

PedyMaster's picture

Hi, thanks for reply!

I have several other services working this way, working with nas without problem even if the service has its own user. Also, when i tried to create the project, folder was created on NAS (when ir was mounted as repo directory), so i dont think this will be the issue, but i will ask gitlab community and post back the answer when i get it.

Jeremy Davis's picture

But thanks for posting back the workaround... It certainly does seem strange though that it creates the folder on first attempt, but still errors...

Jeremy Davis's picture

I guess that leaves you with the option of mounting as the git user or creating a sub folder (owned by the git user)... Or I guess just continuing with your workaround. Thanks again for posting back though... That's awesome info! :)

Add new comment