Add Watchtower error-tracking client - #17
Merged
Merged
Conversation
Same watchtower-ruby path gem Railyard and cclack use — its Railtie wires up the Rack middleware, Rails.error subscriber, Active Job context, breadcrumbs and the performance subscriber. Inert until WATCHTOWER_URL and WATCHTOWER_PUBLIC_KEY resolve, which Railyard injects into the deploy env. Dockerfile: COPY vendor/ (not vendor/*, which flattens subdirs and would hide the path gem's gemspec from bundle install).
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
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.
Vendors the
watchtower-rubypath gem (same client Railyard/cclack use). Railtie auto-wires Rails; inert untilWATCHTOWER_URL/WATCHTOWER_PUBLIC_KEYresolve (Railyard injects them). DockerfileCOPY vendor/fix so the path gem's gemspec is present forbundle install. 305 specs / 0.