Files

T

Ta-Ching ChenandSoam Vasani e587eca08f Add builder manager support (#308 )

This change orchestrates function builds.

Environments (in v2) define a builder image, just like they do a runtime image. The builder image contains a build script that's invoked with source and deployment paths (as env vars).

The buildermgr watches for environments with build images defined, and creates build deployments and services.

Functions can define source and deployment. Buildermgr watches for functions with source code (and build status == pending) and invokes the environment's builder when appropriate. It captures logs from the build and sets the build status (success/failure) and build lots into the PackageStatus.

2017-09-25 07:53:09 -07:00

builder

Add builder manager support (#308 )

2017-09-25 07:53:09 -07:00

Dockerfile

Lighten up the python3 base image (alpine) (#171 )

2017-04-21 11:15:52 -07:00

README.md

Add initial support for PHP7 (#97 )

2017-02-02 11:28:28 -08:00

requirements.txt

Add redis client to python env

2017-01-17 23:42:05 -08:00

server.py

Add builder manager support (#308 )

2017-09-25 07:53:09 -07:00

README.md

Fission: Python Environment

This is the Python environment for Fission.

It's a Docker image containing a Python 3.5 runtime, along with a dynamic loader. A few common dependencies are included in the requirements.txt file.

Customizing this image

To add package dependencies, edit requirements.txt to add what you need, and rebuild this image (instructions below).

You also may want to customize what's available to the function in its request context. You can do this by editing server.py (see the comment in that file about customizing request context).

Rebuilding and pushing the image

You'll need access to a Docker registry to push the image: you can sign up for Docker hub at hub.docker.com, or use registries from gcr.io, quay.io, etc. Let's assume you're using a docker hub account called USER. Build and push the image to the the registry:

   docker build -t USER/python-env . && docker push USER/python-env

Using the image in fission

You can add this customized image to fission with "fission env create":

   fission env create --name python --image USER/python-env

Or, if you already have an environment, you can update its image:

   fission env update --name python --image USER/python-env

After this, fission functions that have the env parameter set to the same environment name as this command will use this environment.