|
1 | | -[](https://github.com/customink/crypteia/actions/workflows/test.yml) |
| 1 | +[](https://github.com/rails-lambda/crypteia/actions/workflows/test.yml) |
2 | 2 |
|
3 | 3 | # 🛡 Crypteia |
4 | 4 |
|
@@ -81,16 +81,16 @@ When building your own Lambda Containers, use both the `crypteia` binary and `li |
81 | 81 |
|
82 | 82 | #### Lambda Containers |
83 | 83 |
|
84 | | -There are two options for Lambda containers. The easiest is to use Docker's multi stage builds with our [Extension Containers]([https://github.com/orgs/customink/packages?ecosystem=container&tab=packages&ecosystem=container&q=extension](https://github.com/orgs/customink/packages?repo_name=crypteia&q=extension)) to copy the `/opt` directory matching your platform and Crypteia version number. example below. Remember to use `-debian` vs `-amzn` if you are using your own Linux containers. Or change the version number depending on your needs. |
| 84 | +There are two options for Lambda containers. The easiest is to use Docker's multi stage builds with our [Extension Containers]([https://github.com/orgs/rails-lambda/packages?ecosystem=container&tab=packages&ecosystem=container&q=extension](https://github.com/orgs/rails-lambda/packages?repo_name=crypteia&q=extension)) to copy the `/opt` directory matching your platform and Crypteia version number. example below. Remember to use `-debian` vs `-amzn` if you are using your own Linux containers. Or change the version number depending on your needs. |
85 | 85 |
|
86 | 86 | ```dockerfile |
87 | | -FROM ghcr.io/customink/crypteia-extension-amzn:latest AS crypteia |
| 87 | +FROM ghcr.io/rails-lambda/crypteia-extension-amzn:latest AS crypteia |
88 | 88 | FROM public.ecr.aws/lambda/nodejs:18 |
89 | 89 | COPY --from=crypteia /opt /opt |
90 | 90 | ENV LD_PRELOAD=/opt/lib/libcrypteia.so |
91 | 91 | ``` |
92 | 92 |
|
93 | | -Alternatively, you can download your platform's binary and shared object file from our [Releases](https://github.com/customink/crypteia/releases) page and place them into your projects Docker build directory. Remember to remove the platform file suffix. Example: |
| 93 | +Alternatively, you can download your platform's binary and shared object file from our [Releases](https://github.com/rails-lambda/crypteia/releases) page and place them into your projects Docker build directory. Remember to remove the platform file suffix. Example: |
94 | 94 |
|
95 | 95 | ```dockerfile |
96 | 96 | RUN mkdir -p /opt/lib |
@@ -136,7 +136,7 @@ S3_BUCKET_NAME=my-bucket ./package/deploy |
136 | 136 | If you are using Crypteia on your own Docker containers without the Lambda Extension mechanics, you can simply set the `ENTRYPOINT` to the Crypteia binary which fetches your environment variables so the shared object preload can use them. |
137 | 137 |
|
138 | 138 | ```dockerfile |
139 | | -FROM ghcr.io/customink/crypteia-extension-amzn:latest AS crypteia |
| 139 | +FROM ghcr.io/rails-lambda/crypteia-extension-amzn:latest AS crypteia |
140 | 140 | FROM ubuntu |
141 | 141 | COPY --from=crypteia /opt /opt |
142 | 142 | ENV LD_PRELOAD=/opt/lib/libcrypteia.so |
|
0 commit comments