phoenix v0.5.0

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

Server to handle automatic code reloading

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

Handles Interacting with Plug.Conn and integration with the Controller layer

Default 404 and 500 error page controller, configured via Mix on each Router

Formats Plug exceptions and handles Error logging

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

This module implements the controller pipeline responsible for handling requests

Plug to handle which Accept headers a Plug stack accepts. Unaccepted mime-types will return a 400 Bad Request response

A plug that simply calls Phoenix’s code reloader

Plug to parse Accept headers for response content-type

Plug to handle request logging at the router level

Defines the Phoenix router

Holds state for multiplexed socket connections and Channel/Topic authorization

Precompiles EEx templates into view module and provides render support

Engines need only to support precompiling a template function, of the form:

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

Handles Topic subscriptions and garbage collection with node failover

Serves as the base view for an entire Phoenix application view layer

Imported into all Phoenix Views for rendering support and template helper functions

Raised when trying to access private conn :phoenix_content_type when it has yet to be fetched