This repository was archived by the owner on Mar 11, 2020. It is now read-only.
When deploying setup the logstreamer on the server #50
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
alexrothenberg
force-pushed
the
logstreamer-on-deploy
branch
from
9b05fbc to
575a6e8
Compare
denis
pushed a commit
that referenced
this pull request
Dec 12, 2017
…nel to master * commit '325909d0a5efbdf391692eb6ad979741358543d7': switch to use new kochiku worker key/cert
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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 automates the manual steps to get the log streamer working. When running
cap deployit1 writes the log streamer port to
kochiku-worker.ymlbased on the port configured inconfig/deploy_hosts.yml2 builds the logstreamer binary using go by performing the 4 steps documented in
logstreamer/README.md