It is a trendy way to provide installation scripts to the users like this:

curl -sSL https://get.blingy.com/ | sh

So, we should keep up with the trend...

$ go get github.com/cross-dev/script-server

$ $GOPATH/bin/script-server -h
Usage: script-server [options] [-|filename]
  -b string
        Base URL pathname (default "/")
  -l string
        Interface and port to listen (default ":41267")
$ $GOPATH/bin/script-server -l 34567 -b /a/b <(echo '{{a}}-{{b}}') >/dev/null 2>&1 &
$ curl -s 'http://localhost:34567/a/b/get?a=oo&b=8'
oo-8

The power of templates comes from the text/template package. I suggest you to read it well as it may take some time before you can harness this power.

The more acquainted ones might want to ask about {{a}} in the example above. How does it work? When a GET request query is extracted and parsed, every parameter becomes a custom closure function. The function simply returns the first value of that parameter. It is handled by the template engine as any other builtin function. It becomes a pipeline and should be respected as such.

The $GOPATH has to be assigned.

$ make

Contributions through PR and issues through issues are welcome.

I think next step would be to begin customizing the said scripts and build them on the fly. Now our blingy.com would accept parameters in the URL query and bake the script content from the template.

The server is done in Go. It is a simple and powerful language, which can easily create HTTP servers and produce textual output from a template.

All parameters passed over the GET request query are parsed and then they are fed to the text processor along with the template. The processor creates output, which becomes an installer script content returned to the client.

• The application does not support HTTPS - proxy it through a secure server
• A customized URL will quickly become hideous and impossible to remember - use URL shortener