Locally deploying #24
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
I did NOT request ts |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request updates the local development workflow by replacing the previous use of the Google Cloud Functions Framework for running individual function endpoints with a new Express-based server. This change simplifies local development by allowing all function endpoints to be served from a single process.
Development workflow update:
devscript inpackage.jsonnow builds the project and starts a local Express server usingdist/tests/deploy.js, instead of running the Google Cloud Functions Framework for each function individually.Local Express server for function endpoints:
tests/deploy.tsfile that creates an Express server, mounts all function handlers fromsrc/functionsat their respective endpoints, and starts listening on a configurable port. This allows you to test all function endpoints locally via HTTP requests.