Shinatra – A simple bash web server (github.com)

not to be that guy, but that's

1. hardly a web server

2. hardly pure bash

of course writing a server of anything in pure bash is a tad bit difficult, as opposed to a client - bash can connect(), but can't bind() / listen() nor accept() unless, of course, you use something to expose these syscalls, but that opens a whole another can of worms...

Whats the point of this?

> Does it work on Windows?

> Of course not.

It works just fine on Windows 10 with WSL.

I think the point here is to demonstrate that one might think that web servers are mystical beasts (true) but after all, they "just" return a HTTP header and some content.

Five lines seems like much when you consider that one can write a concurrent (using threads) C webserver in 12...

I had to look up the colon minus syntax, here's the answer http://stackoverflow.com/questions/10390406/usage-of-in-bash

That was both funny and disappointing. I thought it world at least serve static files. Putting netcat in a for loop is hardly a web server in bash.

Many people here fail to realize, this is an excellent debugging server. I used to have a server to print out the body and headers of requests when building an api to make sure things were going (the right headers and request body) out as expected https://github.com/minhajuddin/httpdebug/blob/master/app.go.

This is a much lighter and nicer version. This is going into my ~/bin/httpdebug :)

You can try sending a few curl requests to see that this really prints the headers and body.

    curl -H "api-key: Foo" -X POST --form name=Khaja http://localhost:8080/

It's more a port responder.

> Is this a thread based server, or does it use an event loop instead?

> No.

Well, which is it ?

Bash (shell-script) is a very powerful language, but a bit too complicated for the non-programmer (computer hacker). Then we got Perl, but it is also a bit too complicated. Now we have JavaScript doing the same thing, but also JavaScript (ES6) is now getting more complicated. I wonder is there a rule that says a (scripting) language for non-programmers will eventually either die or end up being too complicated for non-programmers ?

Clickbait - A web server in one line of bash:

    $ nginx

And the HTTP client:

    exec 3<>/dev/tcp/localhost/8080
    echo -e "GET / HTTP/1.1\n\n" >&3
    cat <&3

While googling for this, found a "Big list of http static servers": https://gist.github.com/willurd/5720255

Not that big.

So this is babys first netcat server? Someone is overly proud of using a command like it was intended...

This reminds me a lot of Certbot's use of the Python SimpleHTTPServer:

  $(command -v python2 || command -v python2.7 || command -v python2.6) -c
  "import BaseHTTPServer, SimpleHTTPServer;
  s = BaseHTTPServer.HTTPServer(('', {port}), SimpleHTTPServer.SimpleHTTPRequestHandler);
  s.serve_forever()"