imaginary

Fast, simple, scalable, Docker-ready HTTP microservice for high-level image processing

MIT License

Stars
5.5K
Committers
56

Bot releases are visible (Hide)

imaginary - v0.1.31

Published by h2non over 7 years ago

v0.1.31 / 2017-05-18

  • feat(version): bump to 0.1.31
  • feat(Dockerfile): use libvips v8.5.5, Go v1.8.1 and bimg v1.0.8
  • Correcting the documentation, caching headers are always sent, regardless of being fetched from mount or by URL. (#133)
  • fix(docs): move toc top level sections
  • feat(docs): add new maintainer notice (thanks to @kirillDanshin)
  • feat(travis): use Go 1.8
  • refactor(docs): update support badges
  • feat(docs): add maintainers section
  • fix(.godir): add project name
  • fix(#124): fast workaround to unblock Heroku deployment until the buildpack can be updated
  • Deploy on Cloud Foundry PaaS (#122)
  • Add backers & sponsors from open collective (#119)
    1. remove the .godir as Heroku and Cloud Foundry remove the support. (#117)
imaginary -

Published by h2non over 7 years ago

imaginary - v0.1.29

Published by h2non almost 8 years ago

  • feat(max-allowed-size): add new option max-allowed-size in bytes
  • fix(max-allowed-size): HEAD response handling
  • fix(usage): correct help message of 'allowed-origins'
imaginary - v0.1.28

Published by h2non about 8 years ago

  • feat(#95): use [email protected].
  • fix(#75): use [email protected], which provides extract area fix.
  • feat(api): supports extend and embed query params. See HTTP API params docs for more details.
  • feat(#94): add placeholder image support in case of error.
  • refactor(heroku): remove defaults flags in Procfile (user most specify them via Heroku app init settings).
imaginary -

Published by h2non about 8 years ago

Changelog

  • feat(#85): add support for authorization headers forwarding to remote image server origins.