Deployment

The bottle run() function, when called without any parameters, starts a local development server on port 8080. You can access and test your application via http://localhost:8080/ if you are on the same host.

To get your application available to the outside world, specify the IP the server should listen to (e.g. run(host='192.168.0.1')) or let the server listen to all interfaces at once (e.g. run(host='0.0.0.0')). The listening port can be changed in a similar way, but you need root or admin rights to choose a port below 1024. Port 80 is the standard for HTTP servers:

# Listen to HTTP on all interfaces
if __name__ == '__main__':
    run(host='0.0.0.0', port=80)

Scaling for Production

The built-in development server is base on wsgiref WSGIServer, which is a very simple non-threading HTTP server implementation. This is perfectly fine for development, but may become a performance bottleneck when server load increases.

The easiest way to increase performance is to install a multi-threaded server library like cheroot or gunicorn and tell Bottle to use that instead of the single-threaded wsgiref server:

run(server='cheroot', ...)   # Pure Python, runs everywhere
run(server='gunicorn', ...)  # High performance

Or using the bottle command line interface:

python3 -m bottle --server gunicorn [...] mymodule:app

For production deployments gunicorn is a really good choice. It comes with its own command line utility that supports a lot more options than bottle. Since Bottle instances are WSGI applications, you can tell gunicorn (or any other WSGI server) to load your app instead of calling run() yourself:

gunicorn -w 4 mymodule:app

This will start your application with 4 gunicorn workers and sane default settings. For more details and more complete examples, check out Gunicorn Documentation.

Server adapters

Bottle ships with a bunch of ready-to-use adapters for the most common WSGI servers so you can try out different server backends easily. You can select a server backend via run(server=’NAME’) or python3 -m bottle –server NAME. Here is an incomplete list:

Name	Homepage	Description
cgi		Run as CGI script
flup	flup	Run as FastCGI process
gae	gae	Helper for Google App Engine deployments
wsgiref	wsgiref	Single-threaded default server
cherrypy	cherrypy	Multi-threaded (deprectated))
cheroot	cheroot	Successor of cheerypy
paste	paste	Multi-threaded, stable, tried and tested
waitress	waitress	Multi-threaded, poweres Pyramid
gunicorn	gunicorn	Pre-forked, partly written in C
eventlet	eventlet	Asynchronous framework with WSGI support.
gevent	gevent	Asynchronous (greenlets)
diesel	diesel	Asynchronous (greenlets)
tornado	tornado	Asynchronous, powers some parts of Facebook
twisted	twisted	Asynchronous, well tested but… twisted
meinheld	meinheld	Asynchronous, partly written in C
bjoern	bjoern	Asynchronous, very fast and written in C
auto		Automatically selects the first available server adapter

Those adapters are very basic and just for convenience, though. If you need more control over your deployment, refer to the server backend documentation and mount your Bottle application just like any other WSGI application.

WSGI Deployment

If there is no adapter for your favorite server or if you need more control over the server setup, you may want to start the server manually. Refer to the server documentation on how to run WSGI applications. Here is an example for cheroot:

import cheroot.wsgi
import mymodule.app

wsgi_server = cheroot.wsgi.Server(
    bind_addr=('0.0.0.0', 80),
    wsgi_app=mymodule.app
)

try:
    wsgi_server.start()
finally:
    wsgi_server.stop()