ShippedSinatra hosting
on Shipped.
A focused Ruby service does not need a complicated deployment. Bring your Sinatra routes and let Shipped run the application around them.
Give a few routes a public address
Sinatra is useful when your app needs a small set of routes with explicit behavior. Package it with a production Rack server and the gems the project uses. Shipped runs that service and handles its public domain and HTTPS, so a local webhook or tool becomes available to its users.
Choose persistence only where you need it
A simple integration may only forward a request, while a useful dashboard needs saved records. Connect PostgreSQL through the Ruby library you prefer and keep credentials in secrets. Store uploaded files or generated exports outside the running process so a new deployment does not erase them.
Keep changes straightforward to review
Ship a local update through your coding agent or use GitHub when the service is maintained in a repository. A staging URL makes it possible to check request signatures, route matching, and returned content. Logs help diagnose a rejected integration request without adding a new framework around the app.
A little more detail
Questions about Sinatra?
Does a Sinatra app need Rails to run on Shipped?
No. Deploy Sinatra with its own Ruby dependencies and production Rack server. Rails is a separate application framework.
Can Sinatra serve HTML as well as JSON?
Yes. Sinatra routes can return different response types and use template libraries. Package the templates and libraries your application uses with the release.
From your workspace to the web