The sws package

[Tags:bsd3, program]

The main drivers for this application were Windows (and Linux) support and security, and to a lesser extent performance. Security is improved over weborf by using Haskell, supporting TLS, and explicitly NOT supporting CGIs of any kind.

[Skip to Readme]


Change log
Dependencies asn1-encoding (==0.9.*), asn1-types (==0.3.*), base (>=4.6 && <4.9), bytestring (==0.10.*), crypto-pubkey (==0.2.*), crypto-random (==0.0.*), directory (==1.2.*), filepath (>=1.3 && <1.5), hourglass (==0.2.*), http-types (==0.8.*), network (==2.6.*), pem (==0.2.*), resourcet (==1.1.*), transformers (==0.4.*), wai (==3.0.*), wai-extra (>=3.0.3 && <3.1), wai-middleware-static (>=0.6 && <0.8), warp (>=3.0 && <3.2), warp-tls (>= && <3.2), x509 (==1.5.*) [details]
License BSD3
Copyright Copyright (c) 2014-2015 Derek Elkins
Author Derek Elkins
Stability Unknown
Category Web
Source repository head: git clone
Uploaded Tue Aug 25 18:17:13 UTC 2015 by DerekElkins
Distributions NixOS:
Downloads 1102 total (5 in the last 30 days)
0 []
Status Docs not available [build log]
Last success reported on 2015-08-25 [all 6 reports]


Maintainer's Corner

For package maintainers and hackage trustees

Readme for sws

Readme for sws-

Simple Web Server

What it is

sws is a self-contained web server that serves files which runs on Linux, Windows and (untested) Mac OS X. Once built, the executable should have no dependencies, e.g., it does not require OpenSSL. Convenience and security are the main goals. It has no config files, and only a few, if any, easily provided command line parameters should be necessary. If convenience and security conflict, I'm willing to sacrifice a little convenience for security, but only a little. Often such conflicts are largely resolvable. For example, requiring a password and using TLS improve security, but making a password or a certificate are inconvenient, so sws can generate these.

Use-case 1: xkcd scenario

You want to send a large file to someone. You browse to the directory containing it, type "sws", and give them your public IP. They browse to it and download. Maybe they are the ones sending the file, but aren't "technical". You browse to an empty directory, type "sws -w", and give them your public IP. They browse to it and upload.

In reality, you need to figure out what your public IP is and open a port in your firewall. sws will currently use Google's STUN server to attempt to figure out your public IP.

Use-case 2: Client-side code demo/development

You build an unhosted web application or you mock out AJAX responses. You can do some simple testing by running "sws -d". (Admittedly, using a file URI will probably work pretty well too, though maybe not so much for mocked POST requests...) You want to show a friend. Just make that "sws".

Use-case 3: Instant read-only Git hosting

git clone --bare /path/to/myrepo ~/public/myrepo.git
cd ~/public/myrepo.git
mv hooks/post-update.sample hooks/post-update
chmod a+x hooks/post-update
git update-server-info
sws --no-compress -H ~/public/


git -c http.sslVerify=false clone

This would be even more instant with darcs.

What it isn't

This is not an app server. It reads and writes files, and that's all it will ever do. There is no way to add code to it. The Haskell ecosystem has plenty of good web frameworks. This is not one of them. It's an application, not a framework. (Well... you could do something with named pipes and/or interesting file systems... but you really shouldn't.)