435c0d9fc8
This PR switches the Nomad repository from using govendor to Go modules for managing dependencies. Aspects of the Nomad workflow remain pretty much the same. The usual Makefile targets should continue to work as they always did. The API submodule simply defers to the parent Nomad version on the repository, keeping the semantics of API versioning that currently exists. |
||
---|---|---|
.. | ||
assetfs.go | ||
doc.go | ||
LICENSE | ||
README.md |
go-bindata-assetfs
Serve embedded files from go-bindata with net/http
.
Installation
Install with
$ go get github.com/go-bindata/go-bindata/...
$ go get github.com/elazarl/go-bindata-assetfs/...
Creating embedded data
Usage is identical to 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.
SPA applications
For single page applications you can use Fallback: "index.html"
in AssetFS context, so if route doesn't match the pattern it will fallback to file specified.
example
import "github.com/elazarl/go-bindata-assetfs"
...
http.Handle("/",
http.FileServer(
&assetfs.AssetFS{Asset: Asset, AssetDir: AssetDir, AssetInfo: AssetInfo, Prefix: "data", Fallback: "index.html"}))