NOTE: This guide is ONLY for devs who don't want to edit their
yarn.lock
file by hand. If you don't care about that please carry on.
So you've pulled the latest master
git checkout master
git pull
production: | |
adapter: postgresql | |
encoding: unicode | |
sslmode: require | |
url: postgres://user:password@host:port/db |
#!/bin/bash | |
BUCKET="YOUR_BUCKET_NAME" # bucket name | |
FILENAME="deployment-package.zip" # upload key | |
TMP_FOLDER="/tmp/lambda-env-tmp/" # will be cleaned | |
OUTPUT_FOLDER="/tmp/lambda-env/" # will be cleaned | |
HERE=${BASH_SOURCE%/*} # relative path to this file's folder | |
LAMBDA_FOLDER="$HERE/lambda/" # relative path |
NOTE: This guide is ONLY for devs who don't want to edit their
yarn.lock
file by hand. If you don't care about that please carry on.
So you've pulled the latest master
git checkout master
git pull
#!/usr/bin/env bash | |
set -o nounset | |
set -o errexit | |
set -o pipefail | |
current_function="$1" | |
current_build="${current_function}_${DEPLOY_ENVIRONMENT}" | |
cd $current_function |