Later on, when working on your dev machine and git prompts you for credentials, use these:.Save the User token name and User token passode of your user. Go to your accout page -> User Token -> click the button, “Acccess user token”.As the user with the nx-developer-git-lfs permissions, log into Nexus Rep Manager.This user needs to have the role nx-developer-git-lfs in Nexus Repo Manager. This user can be a “normal” user or a non-personal technical user or service account. This step is about setting the right roles for the user who’s going to push to Nexus Repo Manager. configure a git-lfs enabled git repository Prepare Nexus Repo Manager Setup the repository where to store git-lfs filesĪn example could be a repository in Nexus named my-gitlfs-hosted-repo, such that the whole Url is Prep user in Nexus Repo Manager for git-lfs.prepare Nexus to be the backend to store the git-lfs files.Ofcourse, I’d also need to push them to a Nexus repo where my “consumer” expects to retrieve them from. As a “consumer”, Nexus is my single source of truth for such binary files or exectables.Īs a “producer”, a git repo would be my source of truth. Thanks to Git LFS (Large File Storage), I can keep them in git while keeping their sizes small because they’ll be stored in Nexus Repo Manager as Git LFS repositories.įrom the perspective of using them, say, consuming them via curl, I’d be getting them from Nexus. But their size and “binary format” makes them unsuited for a git repo. Sometimes I need to keep binaries that I’ll later use during an installation.
0 Comments
Leave a Reply. |