WIP script to provision necessary resources on AWS programmatically. - #170
Open
beporter wants to merge 1 commit into
Open
WIP script to provision necessary resources on AWS programmatically.#170beporter wants to merge 1 commit into
beporter wants to merge 1 commit into
Conversation
The thought with this work is that it would dovetail with the `bootstrap.sh` script, allowing Loadsys to programmatically build a "standard" hosting environment in AWS that was compatible with our app skeleton out of the box. A configuration file would be used to store "answers" to questions about naming, created instance IDs, etc.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The thought with this work is that it would dovetail with the
bootstrap.shscript, allowing Loadsys to programmatically build a "standard" hosting environment in AWS that was compatible with our app skeleton out of the box. A configuration file would be used to store "answers" to questions about naming, created instance IDs, etc.