Version 1.4.1

Summary

This release focus on stability and addresses several bug fixes that reduce errors thrown by the proxy.

Docker Image is available on docker hub: https://hub.docker.com/r/cryptonomictech/nft-image-proxy

Change log

• Added tls support for Postgres connections. The proxy should now be able to connect to databases that require an encrypted connection (#98).
• Fixed resizing failing for very large images (#89).
• Fixed moderation failing when image file size is very close to Rekognition imposed limits (#91).
• Fixed a bug where in moderation reporting was incorrect (#93).
• Fixed missing metrics moderation_hit by re-adding it(#88).
• Added missing Jemallocator runtime config (#90). The proxy will release memory more aggressively now.
• Added a caching layer to store moderation results from the database (#96). This should speed up response time for cached content.
• Added new metrics for capturing usage of the following features: image resizing (#92), the database cache (#96), ipfs fallback gateway (#97), and moderation categories (#95 ).

Upgrade notes

No breaking changes in this version compared to 1.4.0.

Version 1.4.0

Docker Image is available on docker hub: https://hub.docker.com/r/cryptonomictech/nft-image-proxy

Change log:

• Various refactors to consolidate logic, update deps and introduce additional unit tests (#49, #78, #45)
• Various bug fixes (#66, #67, #69, #84, #64).
• The timeout setting for the HTTP client is now configurable. This is specially usefully when fetching large amounts of data from IPFS. See proxy.conf in the repository for an example on how to set this parameter (#56).
• The proxy now supports defining a optional fallback IPFS gateway. This fallback gateway is used in case the content cannot be fetched from the primary gateway. See proxy.conf in the repository for an example on how to set this parameter (#77).
• Added a configurable parameter for specifying the user-agent header when fetching content. See proxy.conf in the repository for an example on how to set this parameter (#43).
• The api key section of the configuration has been redone. Keys are now named. This name is also utilized to show key usage in metrics. The actual key it self is not exposed to the metrics endpoint (#76)
• Added Typedoc to the typescript library (#59).
• Switched moderation logic over to the official AWS SDK (#73).
• Switched to Jemallocator instead of the standard library one. This would mean that memory usage is more predictable in monitoring (#74).
• Various new metrics have been added (#70).

Upgrade notes:

1. There are breaking changes in the configuration file. Specifically the ipfs and apikey sections. See proxy.conf for examples on how to set these for version 1.4.0.
2. The dashboard UI has been deprecated and will be removed in version 2.0.0.
3. Some metrics have been removed as they were broken. New ones have been introduced.

v1.3.0

Docker Image is available on docker hub: https://hub.docker.com/r/cryptonomictech/nft-image-proxy

Changelog:

1. Added an in memory cache. Cache size is configurable via config.
2. Metrics have been redone with several being removed and new ones added. Histogram metrics now have more reasonable buckets.
3. Logging to file with rotation is now supported. See log4rs.yml for more details.
4. The server bind IP can now be specified via config.
5. Fixed a bug where IPFS gateways were returning 0 in the Content-Length header wreaking all sorts of havoc internally.
6. Initial version of the dashboard UI containing the metrics page is out.
7. It is possible to build the proxy on macos.
8. Added minimal CORS support to the proxy.

Upgrade notes:

1. Configuration file has newer entries which are required by the application. Refer to proxy.conf located in the project root for updated entries.