Big list of http static server one-liners

web-servers.md

Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.

Discussion on reddit.

Python 2.x

$ python -m SimpleHTTPServer 8000

Python 3.x

$ python -m http.server 8000

Twisted _^(Python)

$ twistd -n web -p 8000 --path .

Or:

$ python -c 'from twisted.web.server import Site; from twisted.web.static import File; from twisted.internet import reactor; reactor.listenTCP(8000, Site(File("."))); reactor.run()'

Depends on Twisted.

Ruby

$ ruby -rwebrick -e'WEBrick::HTTPServer.new(:Port => 8000, :DocumentRoot => Dir.pwd).start'

Credit: Barking Iguana

Ruby 1.9.2+

$ ruby -run -ehttpd . -p8000

Credit: nobu

adsf _^(Ruby)

$ gem install adsf   # install dependency
$ adsf -p 8000

Credit: twome

No directory listings.

Sinatra _^(Ruby)

$ gem install sinatra   # install dependency
$ ruby -rsinatra -e'set :public_folder, "."; set :port, 8000'

No directory listings.

Perl

$ cpan HTTP::Server::Brick   # install dependency
$ perl -MHTTP::Server::Brick -e '$s=HTTP::Server::Brick->new(port=>8000); $s->mount("/"=>{path=>"."}); $s->start'

Credit: Anonymous Monk

Plack _^(Perl)

$ cpan Plack   # install dependency
$ plackup -MPlack::App::Directory -e 'Plack::App::Directory->new(root=>".");' -p 8000

Credit: miyagawa

Mojolicious _^(Perl)

$ cpan Mojolicious::Lite   # install dependency
$ perl -MMojolicious::Lite -MCwd -e 'app->static->paths->[0]=getcwd; app->start' daemon -l http://*:8000

No directory listings.

http-server _^(Node.js)

$ npm install -g http-server   # install dependency
$ http-server -p 8000

Note: This server does funky things with relative paths. For example, if you have a file /tests/index.html, it will load index.html if you go to /test, but will treat relative paths as if they were coming from /.

node-static _^(Node.js)

$ npm install -g node-static   # install dependency
$ static -p 8000

No directory listings.

PHP _{^{(>= 5.4)}}

$ php -S 127.0.0.1:8000

Credit: /u/prawnsalad and MattLicense

No directory listings.

Erlang

$ erl -s inets -eval 'inets:start(httpd,[{server_name,"NAME"},{document_root, "."},{server_root, "."},{port, 8000},{mime_types,[{"html","text/html"},{"htm","text/html"},{"js","text/javascript"},{"css","text/css"},{"gif","image/gif"},{"jpg","image/jpeg"},{"jpeg","image/jpeg"},{"png","image/png"}]}]).'

Credit: nivertech (with the addition of some basic mime types)

No directory listings.

busybox httpd

$ busybox httpd -f -p 8000

Credit: lvm

webfs

$ webfsd -F -p 8000

Depends on webfs.

IIS Express

C:\> "C:\Program Files (x86)\IIS Express\iisexpress.exe" /path:C:\MyWeb /port:8000

Depends on IIS Express.

Credit: /u/fjantomen

No directory listings. /path must be an absolute path.

Meta

If you have any suggestions, drop them in the comments below or on the reddit discussion. To get on this list, a solution must:

1. serve static files using your current directory (or a specified directory) as the server root,
2. be able to be run with a single, one line command (dependencies are fine if they're a one-time thing),
3. serve basic file types (html, css, js, images) with proper mime types,
4. require no configuration (from files or otherwise) beyond the command itself (no framework-specific servers, etc)
5. must run, or have a mode where it can run, in the foreground (i.e. no daemons)

Update for Elixir (1.17.1):

elixir --no-halt -e 'Application.start(:inets); :inets.start(:httpd, port: 8000, server_root: ~c".", document_root: ~c"./doc", server_name: ~c"localhost", mime_types: [{~c"html",~c"text/html"},{~c"htm",~c"text/html"},{~c"js",~c"text/javascript"},{~c"css",~c"text/css"},{~c"gif",~c"image/gif"},{~c"jpg",~c"image/jpeg"},{~c"jpeg",~c"image/jpeg"},{~c"png",~c"image/png"}])'

This example uses the doc directory for a quick way to locally host/view docs generated with ExDoc.

Here's the more readable version of the string being eval'd, shown as an iex session:

iex(1)> Application.start(:inets)
:ok
iex(2)> :inets.start(:httpd,
...(2)>   port: 8000,
...(2)>   server_root: ~c".",
...(2)>   document_root: ~c"./doc",
...(2)>   server_name: ~c"localhost",
...(2)>   mime_types: [
...(2)>     {~c"html", ~c"text/html"},
...(2)>     {~c"htm", ~c"text/html"},
...(2)>     {~c"js", ~c"text/javascript"},
...(2)>     {~c"css", ~c"text/css"},
...(2)>     {~c"gif", ~c"image/gif"},
...(2)>     {~c"jpg", ~c"image/jpeg"},
...(2)>     {~c"jpeg", ~c"image/jpeg"},
...(2)>     {~c"png", ~c"image/png"}
...(2)>   ]
...(2)> )
{:ok, #PID<0.118.0>}

^ woops- just found this

It's not technically a one-liner, but my use-case is better solved with:

mix do hex.docs fetch + docs && cp -r doc "${HEX_HOME}/docs/hexpm/${OTP_APP}/${OTP_APP_VERSION}" && mix hex.docs offline "${OTP_APP}"

Deno:

deno run --allow-net --allow-read jsr:@std/http/file-server

Powershell:

Install-Module -Name Pode

Start-PodeStaticServer -Port 8085

Serves files from current folder.

https://badgerati.github.io/Pode/Functions/Core/Start-PodeStaticServer/

Newbie start:

Set-ExecutionPolicy unrestricted

Install-Module -Name Pode
Import-Module Pode

Start-PodeStaticServer -FileBrowser -Address 0.0.0.0

Powershell:

Install-Module -Name Pode

Start-PodeStaticServer -Port 8085

Serves files from current folder.

Awesome! But just so we’re clear you are able to do 127.0.0.1:8085 and get a portal but also expose that port externally and it hit the local files in the dir?

Powershell:

Install-Module -Name Pode

Start-PodeStaticServer -Port 8085

Serves files from current folder.

Awesome! But just so we’re clear you are able to do 127.0.0.1:8085 and get a portal but also expose that port externally and it hit the local files in the dir?

with Start-PodeStaticServer -FileBrowser you get a file listing at localhost:8080 / 127.0.0.1:8080 in the current folder

with Start-PodeStaticServer you get index.html serverd by localhost:8080 / 127.0.0.1:8080

with Start-PodeStaticServer -Address 0.0.0.0 binds to all adapters and makes it reachable over network

$ go run github.com/goware/webify@latest -h

@cameronkerrnz

And in case you're wondering where HTTPS is in all this...

Turns out to pretty simple with OpenSSL's s_server utility. I've just used this to help test out a load-balancer configuration before the real backend was ready (not to serve content per-se). The first line creates a self-signed certificate.

openssl req -newkey rsa:2048 -nodes -x509 -subj '/CN=name-you-want.example.com' -days 3650 -out server.cert -keyout server.key
openssl s_server -accept 7781 -cert server.cert -key server.key -WWW

Unfortunately, this does not work for HEAD requests, which is a shame, because the behaviour is to time out.

See the manual page for s_server for more info.

Hello, I tried your snippet command, but I encounter the following error:

Error opening '' mode='r'
80DB80C77E780000:error:80000002:system library:BIO_new_file:No such file or directory:crypto/bio/bss_file.c:67:calling fopen(, r)
80DB80C77E780000:error:10000080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:75:

is this openssl bug? I'm not sure if I understand the error properly

Java has joined the chat:

jwebserver

By default, the server runs in the foreground and binds to the loopback address and port 8000. It serves the current directory.