You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,12 +24,18 @@ Add this line to your project's `Gemfile` and then make sure to `bundle install`
24
24
gem 'lambda_punch'
25
25
```
26
26
27
-
Within your project or [Rails application's](https://lamby.custominktech.com/docs/anatomy)`Dockerfile`, add the following. Make sure you do this before you `COPY` your code. The idea is to implicitly use the default `USER root` since it needs permissions to create an `/opt/extensions` directory.
27
+
Within your project or [Rails application's](https://lamby.custominktech.com/docs/anatomy)`Dockerfile`, add the following. Make sure you do this before you `COPY` your code. The idea is to implicitly use the default `USER root` since it needs permission to create an `/opt/extensions` directory.
28
28
29
29
```dockerfile
30
30
RUN gem install lambda_punch && lambda_punch install
31
31
```
32
32
33
+
LambdaPunch uses the `LAMBDA_TASK_ROOT` environment variable to find your project's Gemfile. If you are using a provided AWS Runtime container, this should be set for you to `/var/task`. However, if you are using your own base image, make sure to set this to your project directory.
34
+
35
+
```dockerfile
36
+
ENV LAMBDA_TASK_ROOT=/app
37
+
```
38
+
33
39
Installation with AWS Lambda via the [Lamby](https://lamby.custominktech.com/) v4 (or higher) gem can be done using Lamby's `handled_proc` config. For example, appends these to your `config/environments/production.rb` file. Here we are ensuring that the LambdaPunch DRb server is running and that after each Lamby request we notify LambdaPunch.
0 commit comments