actionHero.js is a multi-transport API Server with integrated cluster capabilites and delayed tasks.
With actionHero, you create 'actions' which can respond to any type of connection. They process incoming parameters and offer a response to the client. actionHero takes care of routing and responding to each connection type for you.
Learn more about Actions
Background tasks are first-class citizens in actionHero. You can enqueue a task from anywhere in the application. Tasks can be recurring or single-run, and there is also support for running a task across any or all peers in the cluster.
Learn more about Tasks
actionHero uses Faye and Redis to store and share data. With first-class cache functions, decentralized communications, and distributed workers, you can be sure that your application is able to scale from 1 worker on one server, to as big of a cluster as you need.
Learn more about Redis
The actionHero API makes it simple to create a traditional HTTP(s) API, but it also lets you easily extend your API to TCP and websocket clients (all included). actionHero also easily lets you write your own servers to handle custom transports.
Learn more about Servers
actionHero ships with a router to make mapping HTTP requests to your actions a breeze.
Learn more about Routes
actionHero makes API-First development very easy by enforcing a strict separation of views and application logic. actionHero also makes modularizing your application easy with simple clustering and easy-to-use background tasks.
Learn More about API-First development
actionHero (optionally) facilitates real-time communication not only from server-to-client, but also client-to-client! actionHero's chat sub-system allows for streaming of both public and private messages between clients.
Learn more about Chat
It is simple to deploy actionHero with our included binaries. You can launch your server as a single instance or as part of a node.js cluster.
Learn more about Running actionHero
Every respectable framework needs to serve files to its clients (even those that don't speak HTTP), and actionHero is no exception. Configured to asynchronously stream file contents, actionHero provides an excellent file server which can live in parallel with your API routes allowing for a fully featured server. No nginx required!
Learn more about Serving Files with actionHeroactionHero can act as a HTTP or HTTPs API server. With integrated routing, it is easy to create RESTful resources. actionHero can also serve static files.
curl "http://127.0.0.1:8080/api/" -d "action=actionsView"
actionHero ships with the ability to be a line TCP or TLS server. actionHero clients can speak a wire protocol or send lines of JSON. Actions can be processed asynchronously and in parallel. The API server and the built-in chat system provide all you need for a communication or game application.
> telnet localhost 5000
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
{"welcome":"Hello! Welcome to the actionHero api}
> actionsView
actionHero uses Faye to provided a robust and reliable websocket implementation. actionHero web socket clients can fall back to long-polling and other transports to ensure they are connected. actionHero does not require that a client stay connected to the same node.
var A = new actionHeroWebSocket;
A.action("actionsView", function(data){ console.log(data); })
Most importantly, actionHero's modular server architecture allows you to define your own servers and protocols.
Learn how on the actionHero WIKI
npm install actionHero
./node_modules/.bin/actionHero generate
./node_modules/.bin/actionHero start