mirror of https://github.com/fnproject/fn.git synced 2022-10-28 21:29:17 +03:00

Files

Travis Reeder ca18ae88fa Added Lambda Node support as part of the regular functions workflow. (#601 )

* Added Lambda Node support as part of the regular functions workflow.

* Fixes for PR comments.

2017-03-22 21:41:27 +01:00

about.md

Added Lambda Node support as part of the regular functions workflow. (#601 )

2017-03-22 21:41:27 +01:00

aws.md

fn: rename from fnctl (#321 )

2016-11-21 17:24:26 +01:00

create.md

fn: rename from fnctl (#321 )

2016-11-21 17:24:26 +01:00

environment.md

More doc updates, explanation of serverless. (#228 )

2016-11-08 09:44:08 -08:00

getting-started.md

fn: improve UX and publish/deploy command (#359 )

2016-12-01 18:11:13 +01:00

import.md

fn: improve UX and publish/deploy command (#359 )

2016-12-01 18:11:13 +01:00

README.md

Added Lambda Node support as part of the regular functions workflow. (#601 )

2017-03-22 21:41:27 +01:00

test.md

fn: rename from fnctl (#321 )

2016-11-21 17:24:26 +01:00

README.md

Lambda everywhere

Lambda support for IronFunctions enables you to take your AWS Lambda functions and run them anywhere. You should be able to take your code and run them without any changes.

Creating Lambda Functions

Creating Lambda functions is not much different than using regular functions, just use the lambda-node runtime.

fn init --runtime lambda-node <DOCKER_HUB_USERNAME>/lambda-node

Be sure the filename for your main handler is func.js.