From release 17 onward wsgw includes:
* contrib/README.service
* contrib/wsgw.env
* contrib/wsgw.service

The service expects wsgw to be installed at /usr/sbin/wsgw.  To change this, edit the service file appropriately.

Text of README.service copied below


== Systemd Service Unit Files for WSGW ==
The files wsgw.service and wsgw.env provide for running wsgw as a service on
systemd flavors of Linux.  As of writing, many distributions are in the process
of converting to systemd.  wsgw.service has been tested on ArchLinuxARM running
on RaspberryPi, as well as a desktop install of Fedora Core 17.

If you are trying to set up wsgw as a service on an older init.d system (e.g.
Raspbian, Ubuntu), please see README.init


== Installation ==
To add the service to your systemd Linux system, copy wsgw.service to 
  /usr/lib/systemd/system/wsgw.service

wsgw.service expects to have some environment variables set for it so copy
wsgw.env to
  /etc/wsgw.env

You can edit wsgw.env to change the runtime options, add services, etc.  By 
default, wsgw.env just runs a service for pianod.

You should then be able to control the wsgw service using systemctl:
  systemctl start wsgw
  systemctl status wsgw
  systemctl stop wsgw

To set up the service to run at boot:
  systemctl enable wsgw

To disable:
  systemctl disable wsgw


== Support ==
These files are provided as is.  If you need support, you can try asking on the 
pianod mailing list:
  http://lists.deviousfish.com/listinfo.cgi/pianod-deviousfish.com

For RaspberryPi support, you could also try the RaspberryPi forums:
  http://www.raspberrypi.org/phpBB3/