Best Practices for CI/CD w Rivet
I'm looking to add a CI/CD pipeline for my Rivet Unreal project. I already have my Unreal Linux server to Docker process sorted so my only remaining work is really around deployment.
Are there any best practices I should know about for submitting deployments to Rivet? Topics that come to mind:
- build agent auth
- removing older deployments over time
- naming conventions
- docker image size
- rate limits on upload frequency
Are there any best practices I should know about for submitting deployments to Rivet? Topics that come to mind:
- build agent auth
- removing older deployments over time
- naming conventions
- docker image size
- rate limits on upload frequency
Build and scale stateful backends. Rivet Actors is a library for long-lived processes with durable state, realtime, and scalability. Easily self-hostable and works with your infrastructure.
1,419Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
