Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

source the virtualenv environment in the current shell #1

Merged
merged 5 commits into from
May 9, 2016
Merged

source the virtualenv environment in the current shell #1

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
8750ac6
missing command, source the virtualenv environment in the current shell
aureq May 9, 2016
96ba892
typo fix
aureq May 9, 2016
34c7c91
typo fix
aureq May 9, 2016
91f8f18
added instructions for debian distro
aureq May 9, 2016
0a367cb
ignore temporary folders
aureq May 9, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1,3 @@
letslambda.yml
.env
src
19 changes: 16 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,24 +13,37 @@ The configuration file is based on YAML. It should be easy to understand by revi

`domains`: a list of domain information.

- `name`: this is used to configure endpoints, DNS, and CN for the certification
- `name`: this is used to configure endpoints, DNS, and CN for the certification
- `countryName`: is used for countryName in the CSR
- `reuse_key`: will try to reuse the same private key to generate the CSR. This is very useful if you ever want to use Public Key pinning in your mobile app and yet, want to renew your certificates every x months.

## Installation ##

This is the tricky part. This project relies on third party projects that reuires some files to be compiled. Since AWS Lambda runs on Amazon Linux 64 bit, it is important that you have such instance running to prepare your Lambda function.
This is the tricky part. This project relies on third party projects that requires some files to be compiled. Since AWS Lambda runs on Amazon Linux 64 bit, it is important that you have such instance running to prepare your Lambda function.

$> yum install libcffi-devel libyaml-devel gcc openssl-devel git
$> virtualenv .env
$> source .env/bin/activate
$> pip install -r requirements.txt
$> mv .env/lib/python2.7/site-packages/* .
$> mv .env/lib64/python2.7/site-packages/* .
$> mv .env/src/acme/acme/acme* .
$> rm -rf .env
$> zip -r letslambda.zip .

Once this is done, alkl you have to do is to upload your lamnbda function to an S3 bucket.
If you're development environment is running on Debian Linux, you need the following commands:

$> apt-get install -V python-virtualenv python-pip libssl-dev python-dev libffi-dev
$> virtualenv .env
$> source .env/bin/activate
$> pip install -r requirements.txt
$> mv .env/lib/python2.7/site-packages/* .
$> mv .env/lib64/python2.7/site-packages/* .
$> mv .env/src/acme/acme/acme* .
$> rm -rf .env
$> zip -r letslambda.zip .

Once this is done, all you have to do is to upload your lamnbda function to an S3 bucket.

$> aws s3 cp letslambda.zip s3://bucket/

Expand Down