Quickstart
To create a new serverless Flask application really quickly:
- Install pipenv and AWS SAM local and generate app boilerplate:
pip install aws-sam-cli pipenv
sam init --location https://github.com/aws-samples/cookiecutter-aws-sam-python
- Add
flask_serverlessdependency
cd MyApp
make install
pipenv install flask_serverless
- Replace
first_function/app.pycontents with:
from flask_serverless import Serverless, Flask, APIGWProxy
app = Flask(__name__)
Serverless(app)
lambda_handler = APIGWProxy(app)
@app.route('/')
def index():
return "Hello, friend!"
- You're ready to go! Run
make run. Read the README it spits out.
More Coming...
More documentation will be written soon.
Further Reading
1 maintainer
Metadata
1 maintainer
Release files for flask-serverless 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| flask_serverless-0.1.4.tar.gz | 3.3 kB | Without provenance | Details |
Release files / flask_serverless-0.1.4.tar.gz
| Download URL | flask_serverless-0.1.4.tar.gz |
|---|---|
| Size | 3.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
53c2da5b340486604c5b6f784a2d4aa3c51a858a8c20bf7446ec5440b51f0490
|
|
BLAKE2b-256 checksum How to use checksums |
0eba886462db61068e6c8c35af1991213ce592baa26644bd0e673ccdb676d674
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.20.0 setuptools/40.4.3 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.7.0
|
Security for flask-serverless 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
