https://github.com/a-chacon/oas_rage
OasRage is a tool for generating automatic interactive documentation for your Rage APIs. It generates an OAS 3.1 document and displays it using RapiDoc.
https://github.com/a-chacon/oas_rage
api documentation oas3 rage ruby
Last synced: 3 months ago
JSON representation
OasRage is a tool for generating automatic interactive documentation for your Rage APIs. It generates an OAS 3.1 document and displays it using RapiDoc.
- Host: GitHub
- URL: https://github.com/a-chacon/oas_rage
- Owner: a-chacon
- Created: 2025-06-09T22:12:28.000Z (about 1 year ago)
- Default Branch: main
- Last Pushed: 2025-06-14T18:41:02.000Z (12 months ago)
- Last Synced: 2025-12-04T13:57:07.049Z (6 months ago)
- Topics: api, documentation, oas3, rage, ruby
- Language: Ruby
- Homepage: https://a-chacon.com/oas_core
- Size: 235 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
Awesome Lists containing this project
README






# 📃Open API Specification For Rage
OasRage is a tool for generating **automatic interactive documentation for your Rage APIs**. It generates an **OAS 3.1** document and displays it using **[RapiDoc](https://rapidocweb.com)**.
Built for the high-performance [Rage](https://github.com/rage-rb/rage) framework, OasRage leverages Rage's compatibility with Rails and its modern Ruby features, including fiber scheduling for non-blocking I/O. It relies on the [OasCore](https://github.com/a-chacon/oas_core) gem for seamless OpenAPI integration.

## Documentation
For details on how to install, configure, and use OasRage, please refer to the [OasCore MDBook](http://a-chacon.com/oas_core).
## Contributing
Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are **greatly appreciated**. If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star⭐! Thanks again!
If you plan a big feature, first open an issue to discuss it before any development.
1. Fork the Project
2. Create your Feature Branch (`git checkout -b feature/AmazingFeature`)
3. Commit your Changes (`git commit -m 'Add some AmazingFeature'`)
4. Push to the Branch (`git push origin feature/AmazingFeature`)
5. Open a Pull Request
## License
The gem is available as open source under the terms of the [GPL-3.0](https://www.gnu.org/licenses/gpl-3.0.en.html#license-text).
## Star History
[](https://www.star-history.com/#a-chacon/oas_rails&Date)