[3373] Docs - Create set of Rider run configs for internal dev #3396
Conversation
This file contains 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
… to sharing a Postman library between a team); Added --beamable-dev flag to NewMicroservice command (will create the SAMS with the BeamableDev dockerfile) - Moved set-packages.sh script into repo root and added sync-rider-run-settings.sh script to root as well (to share run-configs across team) as a form of discoverability and workflow improvement - Updated template project to contain two Dockerfiles one for beamable developers and another for customers; the BeamableDev one sets us up to build microservice images that reference our own locally built nuget packages
|
Lightbeam link |
|
Lightbeam link |
|
Lightbeam link |
…the new CLI version but an older template.
|
Lightbeam link |
cdhanna
approved these changes
May 21, 2024
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.
Ticket
#3373
Brief Description
Notes
When you are merging a feature branch into
main, please squash merge and make sure the final commit contains any relevent JIRA ticket number. If you are merging frommaintostaging, orstagingtoproduction, please use a regular merge commit.Does this introduce tech-debt? If so, have you added an entry to the Tech-debt document?