配置
局部存储库
To create a Git LFS local repository and enablecalculation of LFS package metadata, from theAdministrationmodule, selectRepositories|Repositories|Localand setGit LFSas thePackage Type.
Remote Repositories
You can create a Git LFSremote repositoryto proxy Git LFS local repositories on other Artifactory instances and enjoy all the features of aSmart Remote Repositories.
To define a Git LFS remote repository,from theAdministrationmodule, selectRepositories|Repositories|Remoteandset its Package Type to beGit LFS, and set the URL of the repository you want to proxy.
Virtual Repositories
A Virtual Repository defined in Artifactory aggregates packages from both local and remote repositories.
This allows you to access both locally hosted binary assets and remote proxied Git LFS repositories from a single URL defined for the virtual repository.
To create a Git LFS virtual repository,from theAdministrationmodule, selectRepositories|Repositories|VirtualandsetGit LFSto be its Package Type,and select the underlying local and remote Git LFS repositories to include under theRepositoriessection.
Make sure you also set theDefault Deployment Repositoryso you can both download from and upload to this repository.
Setting Up the Git LFS Client to Point to Artifactory
In order for your client to upload and download LFS blobs from artifactory the[lfs]clause should be added to the .lfsconfigfile of your Git repository in the following format.
[lfs] url = "https:///api/lfs/ " For example: [lfs] url = "https://localhost:8080/artifactory/api/lfs/lfs-local"
You can also set different LFS endpoints for different remotes on your repo (as supported by the Git LFS client), for example:
[remote "origin"] url = https://... fetch = +refs/heads/*:refs/remotes/origin/* lfsurl = "http://localhost:8081/artifactory/api/lfs/lfs-local"
Copy these clauses using Set Me Up
If you select your Git LFS repository in the Tree Browser and clickSet Me Up,Artifactory will display these clauses in a dialog from which you can simply copy and paste them.
Working with Proxies and HTTPS
When using HTTPS (i.e. behind a proxy) with a self signed certificate your configuration might also require you to add the following:
[http] sslverify = false
Always consult your System Administrator before bypassing secure protocols in this way.
When running Artifactory behind a proxy, defining abase urlis usually required (depending on configuration) due to the operation of the
Git LFS client which expectsto receive redirect urls to the exact upload \ download location of blobs.
LFS repositories must be prefixed with api/lfs in the path
When accessing a Git LFS repository through Artifactory, the repository URL must be prefixed withapi/lfsin the path,except when configuring replication.
For example, if you are using Artifactory standalone or as a local service, you would access your LFS repositories using the following URL:
http://localhost:8081/artifactory/api/lfs/
Or, if you are using Cloud the URL would be:
https://
When configuring replication, reference the repository's browsable url i.e.;
http://localhost:8081/artifactory//
Working with Artifactory without Anonymous Access
By default, Artifactory disallows anonymous access to Git LFS repositories. This is defined in theAdministrationmodule underSecurity | Settings.For details please refer toAllow Anonymous Access.
The Git LFS client will ask for credentials for the Artifactory LFS repo when accessing it - if anonymous access is allowed you can just enter blank credentials, otherwiseyou should enter your Artifactory user name and password (not your Git one).
To make the authentication process automatic you can useGit Credential Helpersto store these for you, and have the Git LFS client authenticate automatically.
Authenticating with SSH
Artifactory supports authenticating your Git LFS client via SSH.
自己通过SSH使用时胃肠道进行身份验证t LFS client, execute the following steps:
- Make sure Artifactory is properly configured for SSH as described in theSSH Server Configuration.
- Upload your SSH Public Key in the SSH section of your user profileas described inConfiguring User Authentication.
- Configure the Git LFS client as follows:
Update theknown_hostsfile with the Artifactory server public key. This file is located under
~/.ssh/known_hosts(and there is also a system-wide file under/etc/ssh/known_hosts).This should take the following format:[]:
For example,[myartifactory.company.com]:1339 ssh-rsa AAAAB3Nza...PC0GuTJT9TlaYD user@domain.com
Update your
.lfsconfigfile at the repository level (not the global level) as follows:ssh: / / USERNAME@美元HOST:$PORT/artifactory/
For example,url = "ssh://git@myartifactory.company.com:1339/artifactory/lfs-local"
Metadata
As the Git LFS client supplies only limited data about the blob being uploaded (only it's sha256 checksum, orOID, and it's size) Artifactory does not store or process any metadata for LFS blobs.
You can set properties on the blobs for your own convenience but this requires extra logic to infer a sha256-named file stored in Artifactory from the actual pointer stored in your Git repository.
Storage
Artifactory stores LFS blobs in a manner similar to the Git LFS client, using the provided sha256 checksum.
Git LFS blobs will be stored under a path such as
Whereadand1bare the 1st and 2nd, and the 3rd and 4th characters in the blob's name respectively.
Git LFS behavior when download from the LFS endpoint fails
The Git LFS client will download the pointer file it created in your remote Git repository if downloading the blob from the LFS endpoint failed (i.e. wrong credentials, network error etc.).
This will cause the actual file in your local repo to be substituted with the pointer created by the LFS clientwith the same nameand lead to any number of problems this behavior can cause.
This is a limitation of the LFS client tracked byissue 89.
Quick Start Guide
Visit our Knowledge Base for aquick start guide of Git LFS with Artifactory.
