Skip to content

Commit c31bc42

Browse files
committed
Update notes
1 parent 3fcbf83 commit c31bc42

File tree

1 file changed

+16
-1
lines changed

1 file changed

+16
-1
lines changed

README.md

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,22 @@ $ yarn start:sls
2323
$ yarn deploy:sls
2424
```
2525

26-
## Note
26+
## Notes
27+
28+
### Developmet Workflow
29+
30+
There's two entrypoints for the server.
31+
32+
- `src/serverless` is where the `handler` function is exported for aws lambda
33+
- `src/main` is for local development
34+
35+
You can develop your app using `start:dev` command, which will run the local nodejs server and regenerate your `schema.gql` file
36+
when update the resolvers.
37+
38+
For serverless development, there's still no solution on this repository to develop with serverless-offline and regenerate the schema on demand.
39+
You can check the `start:sls` script, it's first building and copying over the generated gql file, and then starting the server. PR's are welcome to solve this issue :)
40+
41+
### Deployment
2742

2843
When your function is deployed, you can access `<lambda-url>/dev/graphql` to test with the playground, make sure that your GraphQL Playground
2944
points to `<lambda-url>/dev/graphql` instead of `<lambda-url>/graphql`, otherwise you'll get `403 Forbidden` response.

0 commit comments

Comments
 (0)