General deploy #64
Open
General deploy #64
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
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 does a deploy to a live environment on generic hosting. It doens't push to a "Development" environment yet... so in the case of something like TLSC, we might want to still do something custom. And for that project, using the API versus approval workflow would make more sense.
That said, this gets a start at putting it in CircleCI and allows you to store the credentails securly using a base64 encoded site.alias.yml or a plain text ssh connection string in CircleCI's environment variables.
I'm currently using this on one of my personal sites. Will convert evercurrent over to using it soon.