open-vault/vendor/github.com/elazarl/go-bindata-assetfs
Chris Hoffman e293fe84c3 OSS: Adding UI handlers and configurable headers (#390)
* adding UI handlers and UI header configuration

* forcing specific static headers

* properly getting UI config value from config/environment

* fixing formatting in stub UI text

* use http.Header

* case-insensitive X-Vault header check

* fixing var name

* wrap both stubbed and real UI in header handler

* adding test for >1 keys
2018-04-03 09:34:01 -05:00
..
LICENSE OSS: Adding UI handlers and configurable headers (#390) 2018-04-03 09:34:01 -05:00
README.md OSS: Adding UI handlers and configurable headers (#390) 2018-04-03 09:34:01 -05:00
assetfs.go OSS: Adding UI handlers and configurable headers (#390) 2018-04-03 09:34:01 -05:00
doc.go OSS: Adding UI handlers and configurable headers (#390) 2018-04-03 09:34:01 -05:00

README.md

go-bindata-assetfs

Serve embedded files from jteeuwen/go-bindata with net/http.

GoDoc

Installation

Install with

$ go get github.com/jteeuwen/go-bindata/...
$ go get github.com/elazarl/go-bindata-assetfs/...

Creating embedded data

Usage is identical to jteeuwen/go-bindata usage, instead of running go-bindata run go-bindata-assetfs.

The tool will create a bindata_assetfs.go file, which contains the embedded data.

A typical use case is

$ go-bindata-assetfs data/...

Using assetFS in your code

The generated file provides an assetFS() function that returns a http.Filesystem wrapping the embedded files. What you usually want to do is:

http.Handle("/", http.FileServer(assetFS()))

This would run an HTTP server serving the embedded files.

Without running binary tool

You can always just run the go-bindata tool, and then

use

 import "github.com/elazarl/go-bindata-assetfs"
 ...
 http.Handle("/",
    http.FileServer(
    &assetfs.AssetFS{Asset: Asset, AssetDir: AssetDir, AssetInfo: AssetInfo, Prefix: "data"}))

to serve files embedded from the data directory.