Releases: darklynx/request-baskets
Releases · darklynx/request-baskets
v1.2.3
v1.2.2
Fix in go.mod for "go install"
What's Changed
Full Changelog: v1.2.0...v1.2.1
Serverside configuration and maintenance update
- Migration to Go Modules and GitHub actions, big thanks to @Jackymancs4 (#67)
- New command line parameter to define HTTP path prefix (see #72, #73)
- New command line parameter to run service in restricted mode (see #71, #74)
- Switch from abandoned Bolt project to maintained BBolt (see #70)
- Updated dependencies
- Minor bug and security fixes
Minor UI and service improvements
- Docker container to accept service configuration from outside via environment variables see entrypoint.sh script for the list of supported variables
- Updated external dependencies: httprouter, mysql, pq, etc.
- Minor UI updates:
- a button to copy selected request details to clipboard
- a button to copy basket listening end-point URL to clipboard
- New command line parameter to bootstrap predefined basket(s) at service startup
First major release
- Added new REST API end-points for service stats and version
- UI improvements for admin page to display service statistics
- REST API rework:
- REST API is now available under
/api/*
path including new functionality - Old API paths
/baskets/*
are deprecated but still supported
- REST API is now available under
- Use semantic versioning from now on
Cumulative update of minor fixes
- Improvements and fixes in web UI
- Minor security fixes of forwarding functionality
- Improved docker builds and documentation
Full proxy mode and small UI changes
Baskets now may operate in full proxy mode: when forwarding incoming requests to underlying service the service response can be passed back to clients of original requests. See description of proxy_response
property in basket configuration. Small UI improvements: detailed list of baskets on admin page, individual basket can now be quickly shared with colleagues or friends.
SQL storage for baskets
Implemented support of SQL databases as a storage for baskets and collected HTTP requests. This allows to build more robust and scaleable solutions with Request Basket service by running multiple instances of the service that share the same database storage. See README.md for more details.