Skip to content

Commit 119add6

Browse files
chore: fix images
1 parent ba3016f commit 119add6

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# ![Lambda Live Debugger](logo_landscape_light.svg)
1+
# ![Lambda Live Debugger](public/logo_landscape_light.svg)
22

33
Lambda Live Debugger is an indispensable tool for debugging AWS Lambda functions from your computer, even though they are deployed in the cloud. It supports Lambdas written in JavaScript or TypeScript.
44

@@ -23,7 +23,7 @@ Lambda Live Debugger connects to your deployed Lambda, routes requests to your c
2323

2424
The tool attaches Lambda Extensions (via a Layer), intercepts, and relays calls to AWS IoT. AWS IoT transfers messages between your Lambda and the local machine. If the Lambda is written in TypeScript, it's transpiled to JavaScript. The code is executed via the Node Worker Thread.
2525

26-
![Architecture](./architecture.drawio.png)
26+
![Architecture](./public/architecture.drawio.png)
2727

2828
AWS keys generated on the cloud for Lambda are transferred to the local environment, so the code has the same permissions as it would executed on the cloud. There could be a difference in packaging, mainly regarding static files, which are probably in different locations. You can use additional environment variables to adjust the code:
2929

index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
1-
# ![Lambda Live Debugger_](logo_landscape_dark.svg)
1+
# ![Lambda Live Debugger_](public/logo_landscape_dark.svg)
22

33
<!--@include: ./README.md-->

0 commit comments

Comments
 (0)