2013-05-17 13:13:27 +02:00
|
|
|
The Cowboy Application
|
|
|
|
|
======================
|
|
|
|
|
|
|
|
|
|
Small, fast, modular HTTP server.
|
|
|
|
|
|
|
|
|
|
Dependencies
|
|
|
|
|
------------
|
|
|
|
|
|
|
|
|
|
The `cowboy` application uses the Erlang applications `ranch`
|
|
|
|
|
for listening and accepting TCP connections, and `crypto`
|
|
|
|
|
for establishing Websocket connections. These dependencies must
|
|
|
|
|
be loaded for the `cowboy` application to work. In an embedded
|
|
|
|
|
environment this means that they need to be started with the
|
|
|
|
|
`application:start/{1,2}` function before the `cowboy`
|
|
|
|
|
application is started.
|
|
|
|
|
|
|
|
|
|
The `cowboy` application also uses the Erlang applications
|
2013-06-20 15:24:36 +02:00
|
|
|
`asn1`, `public_key` and `ssl` when listening for HTTPS connections.
|
2013-05-17 13:13:27 +02:00
|
|
|
These are started automatically if they weren't before.
|
|
|
|
|
|
|
|
|
|
Environment
|
|
|
|
|
-----------
|
|
|
|
|
|
|
|
|
|
The `cowboy` application does not define any application
|
|
|
|
|
environment configuration parameters.
|
