GitLab working with GIT Large Files System - how to organize HTTPS authorization?

Question

git

Good afternoon to all participants of the toster project. The crux of the matter is as follows.
I raised it means gitlab on the local machine, using the Omnibus package.
Everything is fine, I created a group in it a repository, commits pass remarkably through ssh keys. Let the repository look like this in SourceTree: [email protected]:testgroup/game_project.git
Decided to connect git LFS following the documentation Turned
on support in omnibus and rebuilt the package.
On the local machine following the documentation
git clone [email protected]:testgroup/game_project.git
git lfs init
git lfs track "*.psd"
git add .
git commit -am "Test PSD file add git LFS"
git push origin master - and here comes the problem. It requires authorization via HTTPS as stated in the documentation. namely, it asks for a password from the git user. How to organize this authorization so that if you want to push LFS, you don’t have to change the repository path to the following 192.168.0.106/testgroup/game_project.git - if I change the repository to http. Everything runs smoothly

git -c diff.mnemonicprefix=false -c core.quotepath=false push -v --tags origin master:master
Pushing to 192.168.0.106/ldgames/1day_game.git
Git LFS: (0 of 1 files) 0 B / 299.38 MB
Git LFS: (0 of 1 files) 299.38 MB / 299.38 MB
POST git-receive-pack (599 bytes)
To 192.168.0.106/ldgames/1day_game.git
3484e92..897fbbf master -> master
updating local tracking ref 'refs/remotes /origin/master'
Succeeded.