Simplify guide to leverage single render.yaml #97
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
Use Node and entry point from their respective absolute paths in the file system
Co-authored-by: bigint <[email protected]>
Co-authored-by: bigint <[email protected]>
Co-authored-by: bigint <[email protected]>
Co-authored-by: bigint <[email protected]>
Co-authored-by: bigint <[email protected]>
akosyakov
force-pushed
the
main
branch
4 times, most recently
from
e5b824a to
76f315f
Compare
akosyakov
force-pushed
the
main
branch
2 times, most recently
from
5b415d5 to
277e9f0
Compare
|
Closing this as we have moved the docs to their own branch, recreated the changes in #97 |
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 PR updates instructions with a simplified deployment process for OpenVSCode behind Oauth. This makes it much easier by using a single render.yaml file for both servers and moving a dependent variable from user-entry into Dockerfile automation.
I have tested all of the links, and this should be my last guide PR until changes to the GitHub auth flow in VSCode come up : ))