Currenty, the function entry is hard-coded to be 'main.main' which is not flexible. This patch adds support for specifying module name and function name in the code package. Change-Id: I92ea36f668073f380a4aef4526a6fad321d8cc95
|6 years ago|
|Dockerfile||6 years ago|
|README.md||6 years ago|
|requirements.txt||6 years ago|
|server.py||6 years ago|
Qinling: Python Environment
This is the Python environment for Qinling.
It's a Docker image containing a Python 2.7 runtime, along with a dynamic loader. A few common dependencies are included in the requirements.txt file. End users need to provide their own dependencies in their function packages through Qinling API or CLI.
Rebuilding and pushing the image
You'll need access to a Docker registry to push the image, by default it's docker hub. After modification, build a new image and upload to docker hub:
docker build -t USER/python-runtime . && docker push USER/python-runtime
Using the image in Qinling
After the image is ready in docker hub, create a runtime in Qinling:
http POST http://127.0.0.1:7070/v1/runtimes name=python2.7 image=USER/python-runtime