You'll notice the server you started earlier handled those requests: Listening LFS on port 9999 Remote: Resolving deltas: 100% (8/8), completed with 4 local objects. Total 16 (delta 8), reused 0 (delta 0), pack-reused 0 Src/_posts/-how-to-be-stingy-git-lfs-s3/-nexus-6p-destroyed.jpg (LFS: 19f2dcd)Ĭommit and push! $ git commit -m "Add example photo"Ĭreate mode 100644 src/_posts/-how-to-be-stingy-git-lfs-s3/-nexus-6p-destroyed.jpg You can tell it's tracked by LFS using git lfs status and checking the LFS tag after the filename: $ git lfs status Now it's time to: Commit a picture to your repoĪdd the image file as you normally would: git add src/_posts/-how-to-be-stingy-git-lfs-s3/-nexus-6p-destroyed.jpg The server will store your files in the bucket at the prefix /git-lfs/ so change that to whatever you like, as long as it's in the format /:user/:repo ( a requirement of the server package at the moment). Url = " This tells git-lfs to use the server running on yor computer for the LFS plugin. lfsconfig file in the base of your git repo with something like: The last thing to do is: Configure the repo to use your local serverĪll you need to do is make a. Now your server is ready for a git-lfs client to connect to it. If you run the script, you should see something like: $ cd lfs-server/ Now the server is fully configured with all the info it needs to store files on S3.
Those environment variables are given to the npx node-git-lfs command, and are consumed by the AWS SDK for Node.js that the server uses.
#Git annex vs git lfs how to#
How To Be Stingy: Git LFS On Your Own S3 Bucket | This is a post on to the commands if you use multiple AWS profiles.
0 kommentar(er)
