Skip to content

Commit fd843cc

Browse files
committed
few more tweaks to READMEs
1 parent bcd176f commit fd843cc

File tree

6 files changed

+17
-68
lines changed

6 files changed

+17
-68
lines changed

Diff for: aws-node-express-api/README.md

+4-24
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ authorAvatar: 'https://avatars1.githubusercontent.com/u/13742415?s=200&v=4'
1515

1616
This template demonstrates how to develop and deploy a simple Node Express API service running on AWS Lambda using the Serverless Framework.
1717

18-
This template configures a single function, `api`, which is responsible for handling all incoming requests using the `httpApi` event. To learn more about `httpApi` event configuration options, please refer to [httpApi event docs](https://www.serverless.com/framework/docs/providers/aws/events/http-api/). As the event is configured in a way to accept all incoming requests, the Express.js framework is responsible for routing and handling requests internally. This implementation uses the `serverless-http` package to transform the incoming event request payloads to payloads compatible with Express.js. To learn more about `serverless-http`, please refer to corresponding [GitHub repository](https://github.com/dougmoscrop/serverless-http).
18+
This template configures a single function, `api`, which is responsible for handling all incoming requests using the `httpApi` event. To learn more about `httpApi` event configuration options, please refer to [httpApi event docs](https://www.serverless.com/framework/docs/providers/aws/events/http-api/). As the event is configured in a way to accept all incoming requests, the Express.js framework is responsible for routing and handling requests internally. This implementation uses the `serverless-http` package to transform the incoming event request payloads to payloads compatible with Express.js. To learn more about `serverless-http`, please refer to the [serverless-http README](https://github.com/dougmoscrop/serverless-http).
1919

2020
## Usage
2121

@@ -40,7 +40,7 @@ Deploying "aws-node-express-api" to stage "dev" (us-east-1)
4040

4141
✔ Service deployed to stack aws-node-express-api-dev (96s)
4242

43-
endpoint: ANY - https://al7bkh7f57.execute-api.us-east-1.amazonaws.com
43+
endpoint: ANY - https://xxxxxxxxxx.execute-api.us-east-1.amazonaws.com
4444
functions:
4545
api: aws-node-express-api-dev-api (2.3 kB)
4646
```
@@ -61,18 +61,6 @@ Which should result in the following response:
6161
{ "message": "Hello from root!" }
6262
```
6363

64-
Calling the `/hello` path with:
65-
66-
```
67-
curl https://xxxxxxx.execute-api.us-east-1.amazonaws.com/hello
68-
```
69-
70-
Should result in the following response:
71-
72-
```json
73-
{ "message": "Hello from path!" }
74-
```
75-
7664
### Local development
7765

7866
The easiest way to develop and test your function is to use the `dev` command:
@@ -83,14 +71,6 @@ serverless dev
8371

8472
This will start a local emulator of AWS Lambda and tunnel your requests to and from AWS Lambda, allowing you to interact with your function as if it were running in the cloud.
8573

86-
In another terminal you can invoke your function by using the following command:
87-
88-
```
89-
curl https://xxxxxxx.execute-api.us-east-1.amazonaws.com/hello
90-
```
74+
Now you can invoke the function as before, but this time the function will be executed locally. Now you can develop your function locally, invoke it, and see the results immediately without having to re-deploy.
9175

92-
Which should result in response similar to the following:
93-
94-
```json
95-
{ "message": "Hello from path!" }
96-
```
76+
When you are done developing, don't forget to run `serverless deploy` to deploy the function to the cloud.

Diff for: aws-node-express-dynamodb-api/README.md

+5-13
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: 'Serverless Framework Node Express API service backed by DynamoDB on AWS'
33
description: 'This template demonstrates how to develop and deploy a simple Node Express API service backed by DynamoDB running on AWS Lambda using the Serverless Framework.'
44
layout: Doc
5-
framework: v2
5+
framework: v4
66
platform: AWS
77
language: nodeJS
88
priority: 1
@@ -15,7 +15,7 @@ authorAvatar: 'https://avatars1.githubusercontent.com/u/13742415?s=200&v=4'
1515

1616
This template demonstrates how to develop and deploy a simple Node Express API service, backed by DynamoDB table, running on AWS Lambda using the Serverless Framework.
1717

18-
This template configures a single function, `api`, which is responsible for handling all incoming requests using the `httpApi` event. To learn more about `httpApi` event configuration options, please refer to [httpApi event docs](https://www.serverless.com/framework/docs/providers/aws/events/http-api/). As the event is configured in a way to accept all incoming requests, the Express.js framework is responsible for routing and handling requests internally. This implementation uses the `serverless-http` package to transform the incoming event request payloads to payloads compatible with Express.js. To learn more about `serverless-http`, please refer to corresponding [GitHub repository](https://github.com/dougmoscrop/serverless-http).
18+
This template configures a single function, `api`, which is responsible for handling all incoming requests using the `httpApi` event. To learn more about `httpApi` event configuration options, please refer to [httpApi event docs](https://www.serverless.com/framework/docs/providers/aws/events/http-api/). As the event is configured in a way to accept all incoming requests, the Express.js framework is responsible for routing and handling requests internally. This implementation uses the `serverless-http` package to transform the incoming event request payloads to payloads compatible with Express.js. To learn more about `serverless-http`, please refer to the [serverless-http README](https://github.com/dougmoscrop/serverless-http).
1919

2020
Additionally, it also handles provisioning of a DynamoDB database that is used for storing data about users. The Express.js application exposes two endpoints, `POST /users` and `GET /user/:userId`, which create and retrieve a user record.
2121

@@ -42,7 +42,7 @@ Deploying "aws-node-express-dynamodb-api" to stage "dev" (us-east-1)
4242
4343
✔ Service deployed to stack aws-node-express-dynamodb-api-dev (109s)
4444
45-
endpoint: ANY - https://jhssgx6g93.execute-api.us-east-1.amazonaws.com
45+
endpoint: ANY - https://xxxxxxxxxx.execute-api.us-east-1.amazonaws.com
4646
functions:
4747
api: aws-node-express-dynamodb-api-dev-api (3.8 MB)
4848
```
@@ -85,14 +85,6 @@ serverless dev
8585

8686
This will start a local emulator of AWS Lambda and tunnel your requests to and from AWS Lambda, allowing you to interact with your function as if it were running in the cloud.
8787

88-
In another terminal you can invoke your function by using the following command:
88+
Now you can invoke the function as before, but this time the function will be executed locally. Now you can develop your function locally, invoke it, and see the results immediately without having to re-deploy.
8989

90-
```
91-
curl https://xxxxxxx.execute-api.us-east-1.amazonaws.com/users/someUserId
92-
```
93-
94-
Which should result in response similar to the following:
95-
96-
```json
97-
{ "userId": "someUserId", "name": "John" }
98-
```
90+
When you are done developing, don't forget to run `serverless deploy` to deploy the function to the cloud.

Diff for: aws-node-http-api/README.md

+3-11
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ Deploying "serverless-http-api" to stage "dev" (us-east-1)
3333
3434
✔ Service deployed to stack serverless-http-api-dev (91s)
3535
36-
endpoint: GET - https://xiz94rsg9g.execute-api.us-east-1.amazonaws.com/
36+
endpoint: GET - https://xxxxxxxxxx.execute-api.us-east-1.amazonaws.com/
3737
functions:
3838
hello: serverless-http-api-dev-hello (1.6 kB)
3939
```
@@ -64,14 +64,6 @@ serverless dev
6464

6565
This will start a local emulator of AWS Lambda and tunnel your requests to and from AWS Lambda, allowing you to interact with your function as if it were running in the cloud.
6666

67-
In another terminal you can invoke your function by using the following command:
67+
Now you can invoke the function as before, but this time the function will be executed locally. Now you can develop your function locally, invoke it, and see the results immediately without having to re-deploy.
6868

69-
```
70-
curl https://xxxxxxx.execute-api.us-east-1.amazonaws.com/hello
71-
```
72-
73-
Which should result in response similar to the following:
74-
75-
```json
76-
{ "message": "Go Serverless v4! Your function executed successfully!" }
77-
```
69+
When you are done developing, don't forget to run `serverless deploy` to deploy the function to the cloud.

Diff for: aws-node-scheduled-cron/README.md

+2-4
Original file line numberDiff line numberDiff line change
@@ -51,8 +51,6 @@ serverless dev
5151

5252
This will start a local emulator of AWS Lambda and tunnel your requests to and from AWS Lambda, allowing you to interact with your function as if it were running in the cloud.
5353

54-
This function will be called every minute by the scheduler; however, you can also manually invoke the function using this command:
54+
Now you can invoke the function as before, but this time the function will be executed locally. Now you can develop your function locally, invoke it, and see the results immediately without having to re-deploy.
5555

56-
```
57-
serverless invoke --function rateHandler
58-
```
56+
When you are done developing, don't forget to run `serverless deploy` to deploy the function to the cloud.

Diff for: aws-node/README.md

+2-13
Original file line numberDiff line numberDiff line change
@@ -63,17 +63,6 @@ serverless dev
6363

6464
This will start a local emulator of AWS Lambda and tunnel your requests to and from AWS Lambda, allowing you to interact with your function as if it were running in the cloud.
6565

66-
In another terminal you can invoke your function by using the following command:
66+
Now you can invoke the function as before, but this time the function will be executed locally. Now you can develop your function locally, invoke it, and see the results immediately without having to re-deploy.
6767

68-
```
69-
serverless invoke --function hello
70-
```
71-
72-
Which should result in response similar to the following:
73-
74-
```json
75-
{
76-
"statusCode": 200,
77-
"body": "{\"message\":\"Go Serverless v4.0! Your function executed successfully!\"}"
78-
}
79-
```
68+
When you are done developing, don't forget to run `serverless deploy` to deploy the function to the cloud.

Diff for: aws-python-flask-api/README.md

+1-3
Original file line numberDiff line numberDiff line change
@@ -15,9 +15,7 @@ authorAvatar: 'https://avatars1.githubusercontent.com/u/13742415?s=200&v=4'
1515

1616
This template demonstrates how to develop and deploy a simple Python Flask API service running on AWS Lambda using the Serverless Framework.
1717

18-
## Anatomy of the template
19-
20-
This template configures a single function, `api`, which is responsible for handling all incoming requests thanks to configured `http` events. To learn more about `http` event configuration options, please refer to [http event docs](https://www.serverless.com/framework/docs/providers/aws/events/apigateway/). As the events are configured in a way to accept all incoming requests, `Flask` framework is responsible for routing and handling requests internally. The implementation takes advantage of `serverless-wsgi`, which allows you to wrap WSGI applications such as Flask apps. To learn more about `serverless-wsgi`, please refer to corresponding [GitHub repository](https://github.com/logandk/serverless-wsgi). Additionally, the template relies on `serverless-python-requirements` plugin for packaging dependencies from `requirements.txt` file. For more details about `serverless-python-requirements` configuration, please refer to corresponding [GitHub repository](https://github.com/UnitedIncome/serverless-python-requirements).
18+
This template configures a single function, `api`, which is responsible for handling all incoming requests thanks to configured `http` events. To learn more about `http` event configuration options, please refer to [http event docs](https://www.serverless.com/framework/docs/providers/aws/events/apigateway/). As the events are configured in a way to accept all incoming requests, `Flask` framework is responsible for routing and handling requests internall y. The implementation takes advantage of `serverless-wsgi`, which allows you to wrap WSGI applications such as Flask apps. To learn more about `serverless-wsgi`, please refer to corresponding [GitHub repository](https://github.com/logandk/serverless-wsgi). Additionally, the template relies on `serverless-python-requirements` plugin for packaging dependencies from `requirements.txt` file. For more details about `serverless-python-requirements` configuration, please refer to corresponding [GitHub repository](https://github.com/UnitedIncome/serverless-python-requirements).
2119

2220
## Usage
2321

0 commit comments

Comments
 (0)