actionHero

actionHero basically provides a well-organized collection of methods to work with TCP, Web sockets, and HTTP clients in Node.js.

The framework facilitates communication between all the parts involved in API queries and responses, working with both HTTP and HTTPS protocols.

actionHero features a modular architecture which allows it to adapt to any project, developers being able to load and use only the parts of the framework they have a need for.

Developers can create their very own "actions" (responses) for the user's queries, respond in real-time to requests, deploy actionHero on a multi-server architecture, include support for serving static assets, and manage a complex task scheduler.

The project is very well documented and should fit any type of project.

What is new in this release:

• Fixes a bug in which actionhero startCluster would fail if the log directory was a symlink.

What is new in version 13.0.1:

• Fixes a bug in which actionhero startCluster would fail if the log directory was a symlink.

What is new in version 12.2.3:

• Support for if-modified-since headers when serving static files.

What is new in version 11.2.2:

• Can now add the configuration apiVersion in your route definitions if you want to point a route to a specific version of an action
• Ensure that the env variable process.env.ACTIONHERO_SHUTDOWN_TIMEOUT is an integer when passed on the command line
• Various fixes for error logging in actions

What is new in version 11.2.1:

• Can now add the configuration apiVersion in your route definitions if you want to point a route to a specific version of an action
• Ensure that the env variable process.env.ACTIONHERO_SHUTDOWN_TIMEOUT is an integer when passed on the command line
• Various fixes for error logging in actions

What is new in version 10.1.1:

• Logger and initializer updates.

What is new in version 10.0.5:

• Can now define defaults, validation, formatting, and requirements in an action's inputs.
• New task processor with auto-scaling of parallel taskProcessors.
• New initializer syntax which allows you to now set init, start, and stop priorities.
• New hooks for say within chatrooms, better blocking callbacks for roomAdd and roomLeave (and the depreciation of the previous authentication APIs).
• New boot options to use multiple config paths / environment variables.

What is new in version 9.4.0:

• Code Coverage and Lint
• Domains
• Dependent packages updated to the latest versions

What is new in version 9.3.0:

• Plugins can now have config files present which will be sourced and merged at runtime
• Move routes.js inside of /config
• If there is a config value which is not present in your project, we will fetch defaults from within the actionHero project
• Organize the grunt tasks into individual files
• Update the new project generator to work with the above
• Adding (optional) redis locks to the cache
• This means you can serve static assets from more than one directory, including within a plugin
• Files will be searched for by the priority with the public root directories are defined

What is new in version 9.2.1:

• Hotfix to allow nested routes.

What is new in version 9.0.0:

• Chat Re-Write, Performance, and Developer Tools.

What is new in version 8.1.0:

• Updates:
• async package updated to v7.0.0
• Fixes:
• Allow empty api.servers.servers on start
• Limit and offset have been removed as default params for connections

What is new in version 8.0.4:

• Bug Fixes:
• Bug which prevented loading servers properly on windows
• Default tests in newly generated actionhero projects to fakeredis=true

What is new in version 8.0.0:

• actionHero V8.0.0 brings the launch of a plugin system.

What is new in version 7.6.8:

• Allows ActionHero to resolve symlinks which change under a running process.

What is new in version 7.6.7:

• Test suite for node v0.8.x runs on travis.ci again. We now test v0.8, v0.9, v0.10 and v0.11
• Upgraded dependent node_modules
• Safety around missing returns from middleware
• Grunt packages moved to optionalDependencies

What is new in version 7.6.6:

• Better support for posting JSON body payloads.

What is new in version 7.6.3:

• Bug Fixes:
• The Task initializer will now shut down before user-generated initializers
• actionhero (in general) will sleep 500ms before exiting to allow any connections more time to exit
• New projects will not be created with a task example
• The "x-powered-by" header is moved to config.js to be user configurable
• The websocket server will not accept new connections when actionHero is shutting down
• The web server will not properly serve the index file for 'deep' public paths

What is new in version 7.6.2:

• Fixed a test case where the specHelper might loop forever (until mocha's timeout).
• Allow config override in gruntfile.
• Obey toRender in specHelper.

What is new in version 7.5.0:

• Websocket clients can now request files.
• node-resque had a minor update.

What is new in version 7.4.2:

• Default new projects with cookies valid on the whole domain.

What is new in version 7.4.1:

• Fixed and tested long-lasting specHelper connections.

What is new in version 7.3.0:

• actionHero now uses grunt as its script-runner rather than Jake.

What is new in version 7.2.0:

• Cache to use a Redis key per object.

What is new in version 7.1.0:

• New Chat Authentication Pattern

What is new in version 7.0.0:

• actionHero now uses resque as its task backend
• The philosophy of any and all tasks has been sacrificed in order to move to resque. All tasks are now any tasks, one and only one server will process that job
• Recurring tasks are still allowed
• Tasks now have a default queue which they will be enqueued into. You can override this at enqueue time
• Tasks may now also opt into specific resque plugins (like worker-lock, which will ensure that only one instance of a job is being processed system-wide at any given time)
• A resque initializer has been added, and the task and taskProcessor initializers have been removed
• Periodic tasks will now automatically be enqueued at boot

What is new in version 6.4.4:

• Buffered stats and bug fixes.

What is new in version 6.4.3:

• MIME-modification should be be action-specific and not global.
• Removing extensions from params caused problems for legitimate use cases where there was a "." in provided data (perhaps sending URLs or sentences).

What is new in version 6.4.1:

• Update defaults for pidfile locations within project.
• Update help.txt to explain environment variable options for project name and config.

What is new in version 6.3.4:

• This tiny release allows you to manually set PROJECT_ROOT as an environment variable to force actionHero to run from a specific directory rather than proces.cwd(). This is useful when deploying actionHero applications on a server where symlinks will change under a running process.

What is new in version 6.3.2:

• Websocket and parsing fixes along with connection middleware.

What is new in version 6.3.0:

• Task workers will not start a new job if sever is mid-shutdown.
• Fix the issue when the parts of the URL are lower parts of the routes.
• Allow server to boot if there no active servers.
• Documentation and project mapping updates.

What is new in version 6.2.7:

• When generating a new actionHero project, configData.general.apiVersion will start at 0.0.1 rather than match actionHero's release version as it has done previously.

What is new in version 6.2.5:

• Allow for relative or local path when describing which config.js to use at boot (--config=/path/to/file).
• Static example site enhancements.

What is new in version 6.2.3:

• actionHero will now provide API documentation to all web clients who visit the /api route with no parameters (GET only). Other clients can request this information with the documentation verb.
• All actions and their metadata will be returned by this response. To hide an action, set action.toDocument = false. This deprecates the actionsView action.

What is new in version 6.2.2:

• This is a minor bug-fix release.

What is new in version 6.2.0:

• This version introduces the ability to run actionHero's methods from the command line.

What is new in version 6.1.0:

• A new reserved param, apiVersion has been introduced. This is used to directly specify the version of an action a client may request.
• If a client doesn't specify an apiVersion, they will be directed to the highest numerical version.
• Can optionally create routes to handle your API versioning.

What is new in version 6.0.1:

• Fixed bugs:
• utils.hashMerge will no longer mangle arrays.
• Initiliazers will now load custom code over base code, allowing overwrites.

What is new in version 6.0.0:

• Server types renamed to "web", "socket", "websocket" for claricy
• Serer types can have options about chatting and such
• The param "file" replaces "fileName" when attempting to directly access the content of files
• Config.js drastically simplified (no more commonWeb, servers block, etc)
• Winston logger object will now be passed into loger config methods

What is new in version 5.1.3:

• When using ./bin/actionHero generateTask, you no longer are required to pass description (name will be used if you don't).
• When using ./bin/actionHero generateAction, you no longer are required to pass description (name will be used if you don't).

What is new in version 5.1.2:

• actionTemplate is the literal action definition, so you can inspect actionTemplate.name, actionTemplate.description, etc..

What is new in version 5.1.1:

• Using the unstable readline module, catching of sigint on windows can be achieved.

What is new in version 5.1.0:

• Tasks will now log their params when starting.
• Tasks will now log their duration when complete.

What is new in version 5.0.0:

• Removed support for node versions < v0.8.0.
• actionHero now uses fakeredis rather than implamenting certain operations locally (cache, tasks).

What is new in version 4.4.0:

• Removed support for node versions < v0.8.0.
• actionHero now uses fakeredis rather than implamenting certain operations locally (cache, tasks).
• This allows for a smaller, more unified codebase.

What is new in version 4.3.5:

• Normalized all connection times to have a connection.sendMessage(message,type) method which can be used globally.
• Fixed error where there were too many commas.
• api.webSockets renambed to api.webSocketServer to be consistant with other servers.

What is new in version 4.3.2:

• for compatibility, only the "http" server will be on at boot.
• Directory creation is now part of the example file logger.

What is new in version 4.3.1:

• Fix logging of master when daemonized.
• Fix daemon server from not being able to detach.
• Disable renaming of the running process. This was not consistent across various operating systems and was confusing.

What is new in version 4.3.0:

• The actionHero server will not exit until any currently processing tasks are complete.

What is new in version 4.2.2:

• Fixed a form parsing bug for Web clients.

What is new in version 4.1.0:

• Tasks will no longer be 'popped' from a queue, but rather slid from queue to queue. This makes it much harder to loose a task.
• There is no longer a need for a periodc task reloader because of the above.
• Tasks can now be easily inspectd, and have been included in the status task.

What is new in version 4.0.7:

• Updates to the actionHeroWebSocket.

What is new in version 4.0.5:

• Various commands have had the room paramite added to thier responses to allow for clarity in the above situation.
• The rooms that a connection is (optionally) additionally interseted in is saved at connection.additionalListiningRooms.
• Can limit the number of actions the server will process at a time for a connection with api.configData.general.simultaniousActions. Defaults to 5.

What is new in version 4.0.3:

• Fixed logging for actionCluster
• Fixed SIGWINCH so only daemonized clusters can use it
• Added in a sweeper for api.cache, so that expired values will be deleted eventually
• Better locking out of internal timers when the cluster is off

What is new in version 3.1.5:

• Allow for api.configData.webSockets.options to contain a hash of settings to be bound to the websocket initalizer (along with .settings which remains an array).

What is new in version 3.1.3:

• Enables to add custom initilizers in a project.

Requirements:

• Node.js 0.6 or higher