Skip to content

Fix docblocks in readme #101

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
josegonzalez merged 1 commit into from
Jul 6, 2023
Merged

Fix docblocks in readme #101

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ A `builder` can be chosen by a flag. Note that while a `builder` may be selected

```shell
lambda-builder build --generate-image --builder dotnet
````
```

#### Building an image

Expand All @@ -81,7 +81,7 @@ By default, any web process started by the built image starts on port `9001`. Th
```shell
# build the image and ensure it starts on port 5000 by default
lambda-builder build --generate-image --port 5000
````
```

Custom environment variables can be supplied for the built image by specifying one or more `--image-env` flags. The `--image-env` flag takes `KEY=VALUE` pairs.

Expand All @@ -94,7 +94,7 @@ The `build-image` and `run-image` can also be specified as flags:

```shell
lambda-builder build --generate-image --build-image "mlupin/docker-lambda:dotnetcore3.1-build" --run-image "mlupin/docker-lambda:dotnetcore3.1"
````
```

A generated image can be run locally with the following line:

Expand Down