From 107740b57d6d4186628a1e053d83261172597b6b Mon Sep 17 00:00:00 2001 From: Leonid Bugaev Date: Sat, 30 Mar 2019 21:30:06 +0700 Subject: [PATCH 1/2] Update README.md --- README.md | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 227e8ff..9a30155 100644 --- a/README.md +++ b/README.md @@ -4,21 +4,18 @@ ## https://goreplay.org/ -## We just released a new version, see announcement https://leonsbox.com/goreplay-v0-16-and-4th-anniversary-5408b1fd72e0 +GoReplay is an open-source network monitoring tool which can record your live traffic, and use it for shadowing, load testing, monitoring and detailed analysis. ## About -GoReplay is the simplest and safest way to test your app using real traffic before you put it into production. - As your application grows, the effort required to test it also grows exponentially. GoReplay offers you the simple idea of reusing your existing traffic for testing, which makes it incredibly powerful. Our state of art technique allows you to analyze and record your application traffic without affecting it. This eliminates the risks that come with putting a third party component in the critical path. -GoReplay increases your confidence in code deployments, configuration changes and infrastructure changes. Did we mention that no coding is required? +GoReplay increases your confidence in code deployments, configuration and infrastructure changes. +GoReplay offers unique approach for shadowing. Instead of being a proxy, GoReplay in background listen for traffic on your network interface, requiring no changes in your production infrastructure, rather then running GoReplay daemon on the same machine as your service. -Here is basic workflow: The listener server catches http traffic and sends it to the replay server or saves to file. The replay server forwards traffic to a given address. - -![Diagram](http://i.imgur.com/9mqj2SK.png) +![Diagram](https://i.imgur.com/IN2xfDm.png) Check [latest documentation](http://github.com/buger/goreplay/wiki). @@ -31,6 +28,7 @@ The most basic setup will be `sudo ./gor --input-raw :8000 --output-stdout` whic If you already have test environment you can start replaying: `sudo ./gor --input-raw :8000 --output-http http://staging.env`. See the our [documentation](https://github.com/buger/goreplay/wiki/) and [Getting started](https://github.com/buger/goreplay/wiki/Getting-Started) page for more info. + ## Newsletter Subscribe to our [newsletter](https://www.getdrip.com/forms/89690474/submissions/new) to stay informed about the latest features and changes to Gor project. From 36ca809e4a5cbbf27f377fb4c8346d4022765bd5 Mon Sep 17 00:00:00 2001 From: Leonid Bugaev Date: Tue, 2 Apr 2019 10:21:26 +0700 Subject: [PATCH 2/2] Add commands to generate rpm/deb --- Makefile | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/Makefile b/Makefile index 20c9538..a663ea9 100644 --- a/Makefile +++ b/Makefile @@ -93,3 +93,20 @@ replay: bash: $(RUN) /bin/bash + + +FPMCOMMON= \ + --name goreplay \ + --description "GoReplay is an open-source network monitoring tool which can record your live traffic, and use it for shadowing, load testing, monitoring and detailed analysis." \ + -v $(VERSION) \ + --vendor "Leonid Bugaev" \ + -m "" \ + --url "https://goreplay.org" \ + -s dir \ + -C /tmp/gor-build \ + +build_packages: + mkdir -p /tmp/gor-build + go build -i -o /tmp/gor-build/gor + fpm $(FPMCOMMON) -a amd64 -t deb ./=/usr/local/bin + fpm $(FPMCOMMON) -a amd64 -t rpm ./=/usr/local/bin