mirror of
https://github.com/gravitational/teleport
synced 2024-10-19 16:53:57 +00:00
61463166c1
This code was unmaintained, created issues with our build system, and didn't actually match the behavior of Teleport's RBAC engine. We will revisit this functionality in the future when we investigate "acess policies as code." |
||
---|---|---|
.. | ||
charts | ||
gomod | ||
macos | ||
pam | ||
pkgconfig | ||
rpm | ||
rpm-sign | ||
tooling | ||
webapps | ||
.bashrc | ||
.gitignore | ||
build-common.sh | ||
build-fido2-macos.sh | ||
build-package.sh | ||
build-pkg-tsh.sh | ||
Dockerfile | ||
Dockerfile-arm | ||
Dockerfile-arm-fips | ||
Dockerfile-centos7 | ||
Dockerfile-centos7-fips | ||
Dockerfile-cron | ||
Dockerfile-fips | ||
Dockerfile-teleterm | ||
install | ||
locale.gen | ||
Makefile | ||
profile | ||
README.md | ||
teleterm_linux_arm64.toolchain.cmake |
Dockerized Teleport Build
This directory is used to produce a containerized production Teleport build. No need to have Golang. Only Docker is required.
It is a part of Gravitational CI/CD pipeline. To build Teleport type:
make
DynamoDB static binary docker build
The static binary will be built along with all nodejs assets inside the container. From the root directory of the source checkout run:
docker build -f build.assets/Dockerfile.dynamodb -t teleportbuilder .
Then you can upload the result to an S3 bucket for release.
docker run -it -e AWS_ACL=public-read -e S3_BUCKET=my-teleport-releases -e AWS_ACCESS_KEY_ID -e AWS_SECRET_ACCESS_KEY teleportbuilder
Or simply copy the binary out of the image using a volume (it will be copied to current directory/build/teleport.
docker run -v $(pwd)/build:/builds -it teleportbuilder cp /gopath/src/github.com/gravitational/teleport/teleport.tgz /builds