phoenix v0.6.1

Compiles Phoenix source files that support code reloading

Creates a new Phoenix application

Prints all routes for the default or a given router

Starts the router or a given worker. Defaults to MyApp.Router

Handles dispatching incoming and outgoing Channel messages

A plug and module to handle automatic code reloading

Controllers are used to group common functionality in the same (pluggable) module

Handles One-time messages, often referred to as “Flash” messages. Messages can be stored in the session and persisted across redirects for notices and alerts about request state

Plug to handle request logging at the controller level

This module implements the controller pipeline responsible for handling requests

Conveniences for working HTML strings and templates

This is an implementation of EEx.Engine and Phoenix format encoder that guarantees templates are HTML Safe

Conveniences for inflecting and working with names in Phoenix

Serves as a Notification and PubSub layer for broad use-cases. Used internally by Channels for pubsub broadcast

Handles PubSub subscriptions and garbage collection with node failover

Defines the Phoenix router

A module used to catch failures and render them using a view

Holds state for multiplexed socket connections and Channel authorization

Templates are used by Phoenix on rendering

The Phoenix engine that handles the .eex extension

Specifies the API for adding custom template engines into Phoenix

The Phoenix engine that handles the .exs extension

Defines a Behaviour for Transport Phoenix.Socket.Message serializiation

Handles WebSocket clients for the Channel Transport layer

Defines the view layer of a Phoenix application

Raised when one of accept* headers are not accepted by the server

Exception raised when no route is found

Exception raised when a template cannot be found

Defines the HTML safe protocol