npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@globocom/backstage-functions

v0.4.7

Published

Remote serverless code executor

Downloads

83

Readme

Build Status Coverage Status

Backstage Functions

Backstage Functions is an Open Source Serverless Platform able to store and execute code.

Benefits

  • Your code will be executed in an isolated environment
  • You don't have to worry about infrastructure
  • Functions can be called at any time by any project

FAQ

  • Which languages are supported? Currently, only Javascript.

  • Is it based on events? Not yet.

  • How the code execution happens in an isolated way? It uses the Backstage Functions Sandbox.

Running locally without Docker

Requirements

  • Redis 3.0+
  • NodeJS 8.13.0

Download the project

git clone https://github.com/backstage/functions.git

Setup

make setup

Run

make run

Configuration

To format your log in json, please run:

export LOG_APP_FORMAT=json

Running locally via Docker

Requirements

  • Docker 1.12+
  • Docker compose 1.8+

Download docker-compose.yml

mkdir functions
cd functions
curl 'https://raw.githubusercontent.com/backstage/functions/master/docker-compose.yml' > docker-compose.yml

Run

docker-compose up

How to use

Function Structure

Your function will have a file, which you define any name you want, and it has to have a function called main, with two parameters: req and res. Req represents the Request and Res represents the Response. At the end of your code, you'll have to use the send method.

Example of a function

function main(req, res) {
  const name = (req.body && req.body.name) || "World"
  res.send({ say: `Hello ${name}!` })
}

Setting a function

To set your function, you can make a PUT request to /functions/:namespace/:name:

curl -i -X PUT http://localhost:8100/functions/example/hello-world \
    -H 'content-type: application/json' \
    -d '{"code":"function main(req, res) {\n  const name = (req.body && req.body.name) || \"World\"\n  res.send({ say: `Hello ${name}! Nice meeting you...` })\n}\n"}'

Ps: if it doesn't exists, it will be created

Deleting a function

To delete your function, you can make a DELETE request to /functions/:namespace/:name:

curl -i -X DELETE http://localhost:8100/functions/example/hello-world \
    -H 'content-type: application/json'

Executing a function

To execute a function, you can make a PUT request to /functions/:namespace/:name/run:

curl -i -X PUT http://localhost:8100/functions/example/hello-world/run \
    -H 'content-type: application/json'

The result will be something like:

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
Content-Length: 22
ETag: W/"16-soBGetwJPBLt8CqWpBQu+A"
Date: Tue, 11 Oct 2016 16:51:04 GMT
Connection: keep-alive

{"say":"Hello World!"}

If one needs to pass an object in the request, the payload is executed:

curl -i -X PUT http://localhost:8100/functions/example/hello-world/run \
    -H 'content-type: application/json' \
    -d '{"name": "Pedro"}'

The result will be something like:

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
Content-Length: 22
ETag: W/"16-Ino2/umXaZ3xVEhoqyS8aA"
Date: Tue, 11 Oct 2016 17:13:11 GMT
Connection: keep-alive

{"say":"Hello Pedro!"}

Executing functions in a pipeline

To execute many functions in a pipeline, you can make a PUT request to /functions/pipeline:

// Function0
function main(req, res) {\
  res.send({x: req.body.x * 10});

}

// Function1
function main(req, res) {
  res.send({x: req.body.x * 20});
}
curl -g -i -X PUT 'http://localhost:8100/functions/pipeline?steps[0]=namespace/function0&steps[1]=namespace/function1' \
    -H 'content-type: application/json'
    -d '{"x": 1}'

Considering the curl above, the pipeline result would be like this:

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
Content-Length: 22
ETag: W/"16-Ino2/umXaZ3xVEhoqyS8aA"
Date: Tue, 11 Oct 2016 17:13:11 GMT
Connection: keep-alive

{"x": 200}