Clone this repo
Use pip to install the code:
pip install --editable .
--editableflag is optional, but very useful in development)
Providing GDAL requires packaging the dependencies GDAL binaries and deps + Python bindings
The repository is shipped with a pre-packaged wheel (GDAL-2.4.0-cp36-cp36m-manylinux1_x86_64.whl) ready to be installed witht he following command:
pip install GDAL-2.4.0-cp36-cp36m-manylinux1_x86_64.whl
The wheel has been built from https://github.com/youngpm/gdalmanylinux running the following commands:
git clone https://github.com/youngpm/gdalmanylinux cd gdalmanylinux make wheel
The command will generete a set of wheels - one for each supported Python version - under gdalmanylinux/wheels directory.
AWS lambdas deployment
In a nutshell, run:
zappa deploy smbbackend # the first time zappa update smbbackend # subsequent deployments set-lambda-env smbbackend
The lambdas can be deployed with zappa. Check the
zappa_settings.json file for more details on available stages.
Deploy a lambda to aws with the following:
zappa deploy smbbackend # first time deployment zappa update smbbackend # subsequent deployments zappa undeploy smbbackend # remove deployment
The AWS console can be used to set environment variables for each lambda
function. In addition, the
smbbackend/awsutils.py file may also be used.
It works by looking at the current local environment and searching for
variables with a special naming. These vars are pushed to the lambda's
This file is also installed as a console script named
you install this package with pip.
Set local environment variables with the following naming convention:
Run the script, providing the name of the zappa stage an argument
For setting the
DB_HOST=somehost env variable for the
savemybike-ingesttrack-dev lambda, you would do the following:
export ZAPPA_SAVEMYBIKE_INGESTTRACK_DEV_DB_HOST=somehost set-lambda-env.py smbbackend
Alternatively you could define all environment files in a file, then export all variables to the current environment and finally run the script
The current zappa configuration expects to find the following environment variables:
AWS_ACCESS_KEY_ID="your-own-aws-access-key-id" AWS_SECRET_ACCESS_KEY="your-own-secret-access-key" AWS_DEFAULT_REGION="aws-region-to-use"
Although it is possible to specify these in the zappa configuration file, we keep their definition outside of it in order to keep the config more portable
Using test data
tests/data directory contains a spatialite DB with some test data. This
data can be loaded by running:
convert-spatialite --output_dir /tmp tests/data/smb_test_data.sqlite DB_HOST="<db-host>" \ DB_NAME="<db-name>" \ DB_USER="<db-user>" \ DB_PASSWORD="<db-password>" \ DB_PORT="<db-port>" \ ingest-tracks <uuid-of-the-user-who-will-own-tracks> /tmp/track_1.csv /tmp/track_2.csv
inges-tracks scripts become available when the
package is installed via pip. They can be combined in order to provide test
data to multiple users