fortio v1.6.0 - dynamic config/flags now optionally web editable!

Big new change in the new dflag support, when adding the flags debug endpoint handler you can now also add a SetFlag handler and URL to enable edits

See standalone example and how it's used in fortio UI

Also simplified the api and better logging for dflag, configmap etc

fortio v1.5.0 - dynamic config/flags!

Pretty big change in this release!

Integrated the (originally go-flagz now dflag) dynamic flag library in fortio
(usable independently as fortio.org/fortio/dflag)
it gives a new flags debugging endpoint: http://localhost:8080/fortio/flags
and a new configmap directory; e.g; -config /etc/fortio and where you can change the loglevel flag dynamically

See dflag for more details on dynamic flags

fortio v1.4.4

Minor addition to the logger. Also v1.4.3 is skipped/accidentally tagged on a branch instead of master.

fortio v1.4.2

New fhttp.LogAndCallNoArg() for handler that do not need the request nor reponse

fortio v1.4.1

Same as v1.4.0 but this time the docker hub auto build worked so we get a docker image tagged

Switched to go1.14 for build
Switched to go modules
Removed the vendor/
Updated dependencies to latest Grpc

fortio v1.4.0

Switched to go1.14 for build
Switched to go modules
Removed the vendor/
Updated dependencies to latest Grpc

fortio v1.3.1

Changes/bug fixes:

• Fixed #312 - 100% error erroneously shown in UI for GRPC tests - thanks @olimpias
• Debian sbuild working (#307) - Help to turn this into an accepted package welcome - @ldemailly
• When using the standard (slow) http(s) client, proxy settings from environment are respected (#317) - thanks @costinm
• In the UI, new + button to add more custom headers (#308) - thanks @SeriyBg

fortio v1.3.0

New/Changes:

• Debian packaging support, new makefile targets: dist, dist-sign, official-install, debian-dist-test, debian-dist

• New location in docker image : /usr/bin/fortio for the binary, /usr/share/fortio for the resources

• Docker volume for data is /var/lib/fortio but the default data directory is "." (current directory) for all installs. That data dir location is now printed at startup, e.g.:

Fortio 1.3.0 grpc 'ping' server listening on [::]:8079
Fortio 1.3.0 https redirector server listening on [::]:8081
Fortio 1.3.0 echo server listening on [::]:8080
Data directory is /Users/ldemailly/go/src/fortio.org/fortio
UI started - visit:
http://localhost:8080/fortio/
(or any host/ip reachable on this server)
11:53:00 I fortio_main.go:213> All fortio 1.3.0 bf3f2d9ff07ed03ef16be56af20d58dc0300e60f go1.11 servers started!

• updated grpc to 1.15

fortio v1.2.2

Changes since v1.2.1: #302 we now build Debian (.deb) and RPM (.rpm) packages

Note: still to do (and help welcome) push those to official ubuntu, etc.. apt repositories (how?)

fortio v1.2.1

This is a minor bug fix (#298) compared to Fortio v1.2.0 + switched the build to use go 1.11 (and corresponding new lint warning fixes), while still being compatible with go 1.8