| commit | 70bd3b72e084e7fc98ab87b9e9414cc54cd04faa | [log] [tgz] |
|---|---|---|
| author | Kelley Spoon <kelley.spoon@linaro.org> | Wed Jun 23 01:59:41 2021 -0500 |
| committer | Kelley Spoon <kelley.spoon@linaro.org> | Wed Jun 23 01:59:41 2021 -0500 |
| tree | 5f784b1934b20460803eca30a231f6436f0dbaf3 | |
| parent | 19c03ee61cdce080ef914fc4f4ad59ffc6070c80 [diff] |
update to support multibucket changes Change-Id: Ib254b1ff1df80a6b298a0f8bee40983268ba92e9
This repository uses Zappa, TuxPut, and pipenv to deploy an upload server to S3!
This will create Pipfile and Pipfile.lock.
$ pipenv install zappa $ pipenv install -e git+ssh://git@gitlab.com/Linaro/tuxput.git@master#egg=tuxput
This will update Pipfile.lock based on the most current version of the things listed in Pipfile.
$ pipenv update
Once it's already been deployed, changes (such as tuxput updates) are deployed using 'zappa update'.
$ pipenv run zappa update dev $ # test/validate dev $ pipenv run zappa update prod
$ CONF_BUCKET=testing-tuxpub-auth S3_REGION=us-east-1 FLASK_APP=tuxput pipenv run flask run
For the time being, there is only one environment: production. The deploy and update verbs require an environment argument.
$ pipenv run zappa deploy prod
To associate a zappa deploy with a domain name, as defined in zappa_settings.yml, run zappa certify. We use ACM certificates to terminate https, which were manually created and are automatically renewed.
$ pipenv run zappa certify prod
You will also need to setup the AWS API Gateway and Route 53 entry for your site. The API Gateway should be tied to the project_name value in zappa_settings.yml.