git-lfs

lfs-test-server

Go2015–2024

git-lfs / lfs-test-server

lfs-test-server

Standalone Git LFS server

Explore on GitHub Read Hacker News discussions

8Distinct people

9Mentions

0Explicit recommenders

795GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Standalone Git LFS server

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

git-lfs/git-lfs · linked in 2 of the same discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 6:01:08 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year9 dated mentions

Observed mentions: 2015-04-08 19:22:48 UTC to 2024-10-19 21:28:52 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
2015	2015-01-01 00:00:00 UTC	2016-01-01 00:00:00 UTC	7	7
2016	2016-01-01 00:00:00 UTC	2017-01-01 00:00:00 UTC	0	0
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	0	0
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	0	0
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	1	1
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	0	0
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	0	0
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	0	0
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	0	0
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	1	1

What Hacker News says

7 sources

bhuga·Oct 24, 2015

I suspect setting up the free LFS reference/test server[1] that GitHub provides would have taken less time than writing this post complaining that GitHub isn't free enough. 1: https://github.com/github/lfs-test-server

In GitHub’s Large File Storage is no panacea for Open Source

m12k·Oct 1, 2015

They do have a reference implementation of the serverside here: https://github.com/github/lfs-test-server - though they themselves don't consider it production ready. But I'm sure it'll either get there in time, or another open source implementation will rise to the challenge (cf. syste's comment about GitLab planning support for this: https://news.ycombinator.com/item?id=10313495 )

In Git Large File Storage 1.0

icey·May 1, 2015

If you're talking about Git-LFS, it's open source: https://github.com/github/git-lfs The API spec is available here: https://github.com/github/git-lfs/blob/master/docs/api.md There's a reference implementation here: https://github.com/github/lfs-test-server

In Improving the GitHub Workflow for the Microsoft Community

heinrich5991·Apr 10, 2015

FWIW the test server is also written in Go: https://github.com/github/lfs-test-server

In Git Large File Storage Is Written in Go

chimeracoder·Apr 8, 2015

> The protocol is open and the client additions are open source. There is a reference server implementation at https://github.com/github/lfs-test-server. This isn't about this particular instance (Github's LFS), but in general, a "reference implementation" isn't the same thing as having an open protocol. Having a reference implementation without a proper specification means that any other implementations have to re-implement the existing reference implementation, including any bugs. The purpose of a specification is to outline undefined behavior as much as it is to outline defined behavior. That is, the specification says, "these are the portions of the program which you may not rely on". We've seen this happen in some languages in which a particular implementation is either the de facto or de jure standard. Other compilers or interpreter

Read the rest

s end up having to mimic their bugs when it comes to things like arithmetic overflow/precision errors, because developers have come to rely on the language behaving one way, in the absence of any clear rules telling them otherwise[0]. [0] Not that developers may not rely on things that a specification explicitly tells them not to - there are plenty of examples of this too - but at least then it's possible to say determine either that a particular program will run on any standards-compliant implementation, or that it is implementation-specific.

In Announcing Git Large File Storage

bhuga·Apr 8, 2015

> tied to GitHub. The protocol is open (https://github.com/github/git-lfs/blob/master/docs/api.md) and the client additions are open source. There is a reference server implementation at https://github.com/github/lfs-test-server. edit: added protocol spec

In Announcing Git Large File Storage

Oompa·Apr 8, 2015

There's an example server that was also open sourced today: https://github.com/github/lfs-test-server

In Announcing Git Large File Storage