Yes, yes, all these one-liner http server are great… but you're missing the point

Knod allows you to POST JSON data to a URL which it stores in a file so you can GET the same data back. If you're prototyping a one page JS app in, say, Ember this means that you don't need work on the backed logic, server or database. It's a pretty smart idea!

I wonder what it does on GET /items though? Hopefully it concatenates all file contents into a JSON array

Yeah, a fake "sticky" backend can be really useful in prototyping a frontend.

I built a similar thing to help with that, built on App Engine (which I usually just run locally): https://github.com/ImJasonH/simply-put

It supports GET/POST/DELETE and simple queries.

I ended up having more fun writing the devel backend than whatever it was I was writing :)

Concatenating the contents into a JSON array is an excellent idea! I'll get to work on that.

Not quite the same, but [Interfake](https://github.com/basicallydan/interfake) is a pretty cool tool for creating mock APIs :-)

Would be even better with a way to do something like this though :-)

While it doesn't support writing (POST/PUT etc), for serving files over HTTP from the current directory, Python's built in HTTP server is perfectly fine. It comes with Python 2.4+ as standard.

    python -m SimpleHTTPServer

Couldn't agree more - if all you need is a static file server, SimpleHTTPServer does the job. I made Knod specifically because I could not find a built in HTTP server that allows writing and deleting.

I'm curious -- what is your use case is for writing and deleting?

Got the idea while working through the React tutorial some time ago. Thought a zero config server that responds to all of the HTTP verbs would make a nice tool for front end prototyping.

"Hey bob, here is a link to a folder on my machine - can you upload that those [random file types] you want me to look at?"

or

"non-tech wife needs to get this file to our home machine, she can use my link to /home/put/ to send this to my home machine from her work"

How is a non-technical person supposed to execute a POST request with an attached file to Knod?

At a guess, using a browser with a file upload form downloaded from the same place where the file will go.

That's fair, although it goes beyond what Knowd provides.

I extended Python SimpleHTTPServer as a data store server for some web games and also as a cross-site XML server for said games. Knod would fit that niche just fine.

I am big fan of the mongoose server[0]. This python thing has issues handling concurrent requests, but i use it as a fallback, if mongoose is not installed.

[0] https://github.com/cesanta/mongoose

I used SimpleHTTPServer for a while, but I found it a bit sluggish at times. I replaced SimpleHTTPServer with http-server, and I've been very pleased with its performance:

https://github.com/nodeapps/http-server

Not standard (or Python), but it's a quick install, and I find it just as usable and much faster.

If you have twisted installed (which is the case on stock OSX), you can use the twisted webserver, which is a lot faster than SimpleHTTPServer and supports concurrent multiple downloads & resumes. I use this alias:

    alias twisted_web='twistd -n web --path $PWD'

And for the python3 folks:

python3 -m http.server

I wish this weren't true, but it's a terrible server - all but unusable. Just try to serve requests to several hosts within the same few seconds.

I don't think it was ever meant to be a server beyond a single user on a single machine. It's great for spinning up a server to start prototyping some web pages, etc. locally. Trying to serve content to multiple users (especially at the same time) is asking for trouble.

    pip install waitress

Is a good choice when you need a little more oomph but not nginx.

or, even better (and supported almost everywhere):

    busybox httpd -p 8080

I have not yet found any boxen having ruby but not busybox httpd.

> I have not yet found any boxen having ruby but not busybox httpd.

Other than OS X?

Same thing for php 5.4+:

php -S localhost:8000

Which (coupled with SQLite) is what I use for all my PHP development stuff. No futzing around with Nginx or Apache configs, and a Phing or Makefile to run `make server` loading my particular dev setup (setting temporary ENV variables and the like) for the project is priceless. That feature is one of my favourites :)

It's an HTTP server that allows reading and writing, hence it is different than the static file servers built into many languages.

So, you can only bind to '0.0.0.0'? Which means, by default, you're opening up read/write to the specified directory without permissions, to the entire world?

Maybe the default should be 127.0.0.1; and if the user specifies 0.0.0.0 then it comes with a big fat warning?

I have worked on a similar server off and on, but it was mostly for GET/PUT-ing HTML files (and not JSON data). That way you could put the contents of `document.documentElement.outerHTML` right back to where the page was retrieved from. The developer tools of the browser, as well as `contenteditable` can be used to create a relatively convenient HTML/content editor.

Additionally the pages were retrieved/saved from a local bare git repository and when some file was PUT it would be saved in a new commit and the branch would be updated. It allowed more collaboration, since multiple people could work on the same page without overwriting each others work.

Anonymous editing isn't yet implemented, but the idea is to have anyone being able to make changes (with some restrictions) and offer it to the site's owner (kind of like a pull request). It would allow wiki-like functionality for websites in general.

Javascript was used for more specialized editing tools, like adding rows to certain tables and calculating totals (for example for [HTML5 invoices](http://www.jonathantneal.com/blog/the-html5-invoice/)). Remove DOM elements when you're done editing and PUT the page back.

Recently I felt a bit constricted with this model, since some parts of the pages needed to be reused across multiple pages (like 'master pages' or blogpost entries). I've implemented a simple 2-way templating engine. Static pages can be built from the templates and from the page you could extract the templates, without losing data. That way you could edit the page as-is, but the parts that are templated are saved in the template (and reused in other pages). It did make the server more complex than a simple GET/PUT server, but the GET/PUT functionality was still preserved.

I see a lot of potential in such a GET/PUT server. With the right permissions for PUT operations, this can also be quite a decent 'CMS'-like server.

Ruby already has the ability to spin up a quick webserver for the current directory. This is supported through the un file in Ruby's stdlib: http://ruby-doc.org/stdlib-2.0.0/libdoc/un/rdoc/Object.html.

    ruby -run -e httpd -- --port=8080 .

Say no more!.

Looks good. I wrote something similar, a small gem called Ferver, no writes but you can point it to any directory then list or download files. Built on top of Sinatra.

https://github.com/rob-murray/ferver

Just chiming in with Node's http-server: https://www.npmjs.org/package/http-server

This has noticeably better performance than the python built-in http server in my experience.

That's why I prefer it. A dev site with a bunch of resources could wedge the SimpleHTTPServer every couple of page loads. Still haven't overwhelmed http-server.

Why not use couchDB? It's marginally more work to deal with the _rev when updating a document, but you've then got a much more useful prototype.

Because then you need another webserver for the static files.

I get this:

`<class:Server>': undefined method `using' for Knod::Server:Class (NoMethodError)

Am I a loser?

It requires Ruby 2.1

You can do this in ruby using:

    ruby -run -e httpd . -p 5000