Categorygithub.com/git-lfs/lfs-test-server
modulepackage
0.4.0
Repository: https://github.com/git-lfs/lfs-test-server.git
Documentation: pkg.go.dev

# README

LFS Test Server

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.

See CONTRIBUTING.md for info on working on LFS Test Server and sending patches.

Installing

Download the latest version. It is a single binary file.

Alternatively, use the Go installer:

  $ go install github.com/github/lfs-test-server

Building

To build from source, use the Go tools:

  $ go get github.com/github/lfs-test-server

Running

Running the binary will start an LFS server on localhost:8080 by default. There are few things that can be configured via environment variables:

LFS_LISTEN      # The address:port the server listens on, default: "tcp://:8080"
LFS_HOST        # The host used when the server generates URLs, default: "localhost:8080"
LFS_METADB      # The database file the server uses to store meta information, default: "lfs.db"
LFS_CONTENTPATH # The path where LFS files are store, default: "lfs-content"
LFS_ADMINUSER   # An administrator username, default: unset
LFS_ADMINPASS   # An administrator password, default: unset
LFS_CERT        # Certificate file for tls
LFS_KEY         # tls key
LFS_SCHEME      # set to 'https' to override default http
LFS_USETUS      # set to 'true' to enable tusd (tus.io) resumable upload server; tusd must be on PATH, installed separately
LFS_TUSHOST     # The host used to start the tusd upload server, default "localhost:1080"

If the LFS_ADMINUSER and LFS_ADMINPASS variables are set, a rudimentary admin interface can be accessed via http://$LFS_HOST/mgmt. Here you can add and remove users.

To use the LFS test server with the Git LFS client, configure it in the repository's .gitconfig file:

  [lfs]
    url = "http://localhost:8080/"

HTTPS:

NOTE: If using https with a self signed cert also disable cert checking in the client repo.

	[lfs]
		url = "https://localhost:8080/"

	[http]
		sslverify = false

An example usage:

Generate a key pair

openssl req -x509 -sha256 -nodes -days 2100 -newkey rsa:2048 -keyout mine.key -out mine.crt

Make yourself a run script

#!/bin/bash

set -eu
set -o pipefail


LFS_LISTEN="tcp://:9999"
LFS_HOST="127.0.0.1:9999"
LFS_CONTENTPATH="content"
LFS_ADMINUSER="<cool admin user name>"
LFS_ADMINPASS="<better admin password>"
LFS_CERT="mine.crt"
LFS_KEY="mine.key"
LFS_SCHEME="https"

export LFS_LISTEN LFS_HOST LFS_CONTENTPATH LFS_ADMINUSER LFS_ADMINPASS LFS_CERT LFS_KEY LFS_SCHEME

./lfs-test-server

Build the server

go build

Run

bash run.sh

Check the managment page

browser: https://localhost:9999/mgmt

# Functions

ContentMatcher provides a mux.MatcherFunc that only allows requests that contain an Accept header with the contentMediaType.
MetaMatcher provides a mux.MatcherFunc that only allows requests that contain an Accept header with the metaMediaType.
NewApp creates a new App using the ContentStore and MetaStore provided.
NewContentStore creates a ContentStore at the base directory.
NewKVLogger creates a KVLogger that writes to `out`.
NewMetaStore creates a new MetaStore using the boltdb database at dbFile.
NewTrackingListener creates a new TrackingListener, listening on the supplied address.

# Variables

Config is the global app configuration.

# Structs

App links a Router, ContentStore, and MetaStore to provide the LFS server.
No description provided by the author
No description provided by the author
Configuration holds application configuration.
ContentStore provides a simple file system based storage.
KVLogger provides a logger that logs data in key/value pairs.
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
MetaObject is object metadata as seen by the object and metadata stores.
MetaStore implements a metadata storage.
MetaUser encapsulates information about a meta store user.
No description provided by the author
Representation is object medata as seen by clients of the lfs server.
RequestVars contain variables from the HTTP request.
TrackingListener tracks incoming connections so that application shutdown can wait until all in progress connections are finished before exiting.
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author

# Type aliases

No description provided by the author