{{ message }}
Serverless Python
Various popular python libraries, pre-compiled to be compatible with AWS Lambda
A full featured walkthough of using django on zappa (powered by AWS Lambda in serverless environment)
Zappa Docker image based on Lambda compatible base
Serverless image generator that uses XKCD comic as basis for _all_ excuses!
Automated tracing library for Python 2.7, 3.6, 3.7 and 3.8
A Vagrant box for development on Python 3.6, with many extras for Django 2.x development.
Create a AWS VPC with associated resources for use with Zappa
Sign AJAX/CORS requests on AWS Lambda for direct browser to S3 uploads
Create a Serverless Web Application using Zappa, AWS Lambda, and Django.
Monitor your AWS Elastic Beanstalk environment in different regions with a health dashboard.
Run ffmpeg inside a lambda for serverless transformations.
Vue.js, Flask, and Firebase
A quick walkthrough setting up a new authenticated serverless app using Zappa and Cognito
Serverless Image Processing Service
Flask service for liquid-rescaling images using ImageMagick inspired by http://contentawaresatan.com/, deployable on AWS API Gateway/Lambda.
Serverless comments for any website
API with info for ATMs (cajeros) in Mexico
Telegram Bot Lambda Boilerplate using Zappa + Hug + Telepot
Threat Response Serverless Relay Template
Add a description, image, and links to the zappa topic page so that developers can more easily learn about it.
To associate your repository with the zappa topic, visit your repo's landing page and select "manage topics."
Right now settings are just passed in through the settings file. This is somewhat limiting if there is a value that will be dynamic with deployments (such as a docker image file, etc.) We should support accepting settings through environment variables, the CLI, the current settings file, and any mix of those.
The order of precedence with mixed should be CLI -> environment -> config file.
If