posted by chriskapp on
We are really excited to announce version 1.0.0-RC3 of Fusio.
First we want to thank our community for the great feedback which we have
received in the last month. With the last 0.9.9 release announcement
we got a huge attention boost and increase of our website and github followers.
We have received great feedback from many different people and we are ready to
push the platform to the next stage.
We have already implemented many useful features and fixed various bugs in
the last releases. Since we are on our way to the first stable release we dont want
to include any new major changes to the platform. We will use the next upcoming
RC* releases to test Fusio on different platforms and for fine-tuning.
So if you want to support the project please follow us on GitHub
or Twitter.
If we have reached the first stable release we would like to concentrate on documentation and marketing of the project. Our main goal of the project is to enable every developer to build a modern API without implementing the complicated parts of an API like authorization, rate limiting, specifications, documentation, etc. True to this motto we plan to improve the documentation with recipes for specific use cases and we want to extend our video tutorials. If you have any documentation ideas or topics please let us know.
ChangelogThere were many great changes between the last blog post and this release. To keep it short I will summarize the important changes to keep you up to date.
By default Fusio comes now with the Swagger-UI app which should help users to start using the API.
Because of the Swagger-UI app we have greatly improved our generated OpenAPI specification. We document now all authentication methods and scopes so that its easy possible to call protected endpoints.
Previously HEAD and OPTIONS requests were not correct
handled by the API endpoints which produced some problems for CORS
or monitoring services which is now fixed.
We have added a new cronjob service which can be used to call actions
in a specific interval. Therefor Fusio generates a custom cron file which can
be placed at i.e. /etc/cron.d/fusio. Every time a user creates or updates
a cron entry this file gets regenerated.
Fusio supports now the handling of PATCH requests.
We have added a new processor to serve simply static json files. This can be useful for testing and quickly mocking an API.
We have added an OAuth2 refresh token endpoint so that its possible to extend an existing access token at our repository.
You can also take a look at the complete changelog.