ShippedRocket hosting
on Shipped.
Take your Rocket routes and request guards online. Shipped runs your compiled application and connects the infrastructure around it.
Package the routes and files your app needs
A Rocket deployment needs the compiled program plus any templates, static files, and libraries it expects at runtime. Include those in a production container and run the service with the appropriate configuration. Shipped gives it a public URL while your application handles its routing, guards, and responses.
Keep production secrets outside the release
Configure the application for the deployed address and port, and keep signing keys and database credentials in secrets. Connect a persistent database for application records. If private cookies or other encrypted values depend on a stable key, preserve that key across releases instead of generating a new one each time.
Test guards and error handling in staging
Use a separate environment to check forms, validation, request guards, and error catchers before making a release public. Test both missing and valid credentials against protected routes. Deploy through your agent or GitHub and inspect service logs when the application rejects or fails a request.
A little more detail
Questions about Rocket?
Do Rocket templates get compiled into the binary automatically?
That depends on the template integration and application setup. Package all files your production program reads at runtime and test the resulting image.
Where should I keep a Rocket secret key?
Use stable secret configuration for a production key and load it through the configuration mechanism your app supports. Do not commit it into the repository or change it as an accidental part of deployment.
From your workspace to the web