- Reference Documentation - Reference
- Technical Documentation(Rust) - Markdown
- An article showcasing multiple usage examples - DEV Community
- Technical Documentation(CPP) - Coming Soon
render_cdk
provides a streamlined interface for interacting with Render, a platform that allows you to build, deploy, and scale your apps with ease. This crate abstracts Render's API, making it easier to work with Render cloud programmatically.
- Name: render_cdk
- Version: 0.0.21
- License: MIT
Work on the resource management module is currently under way. The API supports many of the same actions available from the Render Dashboard. It currently provides endpoints for managing:
- Services
- Deploys
- Custom domains (Coming Soon)
- Jobs (Coming Soon)
The CDK will provide an abstraction that will make it easier to work with the Render cloud programmatically.
The render_cdk
crate provides a comprehensive toolkit for managing cloud environments, IaaS, resource management, and state management within a Continuous Deployment/Continuous Integration (CDK) environment. This documentation provides an overview of the primary components and usage examples to help you get started.
- environment_management: Tools and utilities for managing the deployment environment.
- iaas: Infrastructure as a Service functionalities.
- resource_management: Tools for managing resources, including models and utilities.
- state_management: Utilities for managing the state of deployed services.
- logger: Logging utilities for debugging and tracking operations.
To use render_cdk
, include the following in your Cargo.toml
:
[dependencies]
render_cdk = "0.0.21"
- Examples can be found in the: Technical Documentation
Contributions are welcome! Please see the repository for more information on how to contribute.
This project is licensed under the MIT License. See the LICENSE file for details.
For questions, issues, or suggestions, please open an issue on the repository.
Thank you for using render_cdk
! We hope this documentation helps you get started quickly.
Automate tests for deployed services e.g Connecting and running queries on created database instances etc.