ShippedActix hosting
on Shipped.
Give your Actix Web application a live home. Keep its handlers and middleware while Shipped runs the service around them.
Run the web application you have built
Package your Actix Web binary and the runtime dependencies it needs, then deploy it as a web service. Your app continues to own route registration, request extraction, and response behavior. Shipped handles the public address and HTTPS, connecting customers and clients to the HTTP server you provide.
Keep shared data intentional
Application state can give handlers access to database pools, configuration, and other clients. Use persistent services for records that must outlive the process, and supply their credentials through secrets. If the application runs multiple processes or replicas, do not assume their in-memory values form one shared data store.
Make a production release observable
Log enough request and application context to investigate failures without logging private tokens or customer secrets. Use staging to check middleware and database interactions before release. Your coding agent or GitHub can deploy the new version, and deployment history gives you an earlier app release to restore when needed.
A little more detail
Questions about Actix?
Are Actix and Actix Web the same thing?
Actix Web is the web framework covered by this hosting page. The Actix actor framework is a separate part of the ecosystem; your application determines which libraries it uses.
Can handlers share a database connection pool?
Yes, through the application state pattern your project uses. The database remains the durable data store, and the pool is a runtime connection resource that the app initializes.
From your workspace to the web