Displaying 1 to 11 from 11 results

Git Large File Storage - Git extension for versioning large files

  •    Go

Git LFS is a command line extension and specification for managing large files with Git. The client is written in Go, with pre-compiled binaries available for Mac, Windows, Linux, and FreeBSD.

SparkleShare - Share and collaborate by syncing with any Git repository instantly

  •    CSharp

SparkleShare is a file sharing and collaboration app. It works just like Dropbox, and you can run it on your own server. It's available for Linux distributions, macOS, and Windows. Support the project on Patreon. SparkleShare creates a special folder on your computer. You can add remotely hosted folders (or "projects") to this folder. These projects will be automatically kept in sync with both the host and all of your peers when someone adds, removes or edits a file.

lfs-test-server - Standalone Git LFS server

  •    Go

LFS Test Server is an example server that implements the Git LFS API. It is intended to be used for testing the Git LFS client and is not in a production ready state.LFS Test Server is written in Go, with pre-compiled binaries available for Mac, Windows, Linux, and FreeBSD.

build-dockers - Dockers for building git-lfs

  •    Shell

These dockers are designed specifically for use on github/git-lfs repo. See the docker directory for more information on using these dockers.To make docker tags in the automated build, you have to create a git branch/tag and map that to a docker tag. While master is the main development branch for this repo, it did not make sence to branch and update a Dockerfile in different branches. Instead, the commit_tags.bsh script will execute docker+ and generate the Dockerfiles for each tag and then commit them. This way you develop on master, and when you are ready to releast, run commit_tags.bsh and then push the tags. Note, you will have to do a force push to update the tags.




ue4-gitignore - A git setup example with git-lfs for Unreal Engine 4 projects.

  •    

A correct git setup example with git-lfs for Unreal Engine 4 projects. This template implies some conventions to be used correctly, which are discussed below. You should be able copy and paste them into your project's README.md if you want to.

Git-It-GUI - A Git GUI client designed to be simple with game studio collaboration in mind.

  •    CSharp

Invokes git commands directly allowing any filters to work (including git-lfs). Writen in C# / WPF (will support macOS and Linux/BSD in the future with Xamarin.Forms 3.0).

UE4GitPlugin - Unreal Engine 4 Git LFS 2 Source Control Plugin (beta)

  •    C++

UE4GitPlugin is a simple Git Source Control Plugin for Unreal Engine 4.18. You need to install it into your Project Plugins/ folder, and it will overwrite (replace) the default "Git (beta version)" Source Control Provider with the "Git LFS 2" plugin.

git-lfs-fetch.py - Lightweight Git Large File Storage fetcher written in python

  •    Python

A lightweight Git Large File Storage fetcher written in python. This module cannot fully replace the official git-lfs client, it only knows how to download the files, cache them (the same way the official client does), and place them in a checkout directory. Uploading files is not implemented at all.


git-as-svn - Subversion frontend server for git repository (java)

  •    Java

This project is an implementation of the Subversion server (svn protocol) for git repository. It allows you to work with a git repository using the console svn, TortoiseSVN, SvnKit and similar tools.

lfscache - LFS Cache is a caching Git LFS proxy.

  •    Go

lfs-cache is a caching proxy for Git LFS servers. Download the correct binary for your system.

piggyback - :package: for using large(r) data files on GitHub

  •    R

Because larger (> 50 MB) data files cannot easily be committed to git, a different approach is required to manage data associated with an analysis in a GitHub repository. This package provides a simple work-around by allowing larger (up to 2 GB per file) data files to piggyback on a repository as assets attached to individual GitHub releases. These files are not handled by git in any way, but instead are uploaded, downloaded, or edited directly by calls through the GitHub API. These data files can be versioned manually by creating different releases. This approach works equally well with public or private repositories. Data can be uploaded and downloaded programmatically from scripts. No authentication is required to download data from public repositories. See the piggyback vignette for details on authentication and additional package functionality.