# Running the web server

Once Supysonic is installed and configured, you’ll have to start its web server for the clients to be able to access the music. Here you have several options, whether you want to run it as independant process(es), then possibly putting it behind a reverse proxy, or running it as a WSGI application within Apache.

## supysonic-server

But the easiest might be to use Supysonic’s own server. It actually requires a WSGI server library to run, so you’ll first need to have either Gevent, Gunicorn or Waitress to be installed. Then you can start the server with the following command:

    supysonic-server

And it will start to listen on all IPv4 interfaces on port 5722.

This command allows some options, more details are given on its manpage: supysonic-server.

## Other options

You’ll find some other common (and less common) deployment option below:

- Standalone WSGI Containers
  - Gunicorn
  - uWSGI
  - Waitress
- Apache and mod_wsgi
  - Installing mod_wsgi
  - Creating a .wsgi file
  - Configuring Apache
- Other options
  - FastCGI
  - CGI

As Supysonic is a WSGI application, you have numerous deployment options available to you. If you want to deploy it to a WSGI server not listed here, look up the server documentation about how to use a WSGI app with it. When setting one of those, you’ll want to call the `create_application()` factory function from module `supysonic.web`.