ASP.NET Core hosting
on Shipped.
Ship your ASP.NET Core application with the server and configuration it needs. Keep your controllers, pages, and middleware together.
Give your published app a public endpoint
Deploy the ASP.NET Core publish output with a compatible runtime and its application server. Shipped routes traffic to the service and handles the public domain and HTTPS. Keep the app’s port, proxy handling, and environment settings aligned with the deployment so redirects and generated URLs behave correctly.
Connect pages and APIs to persistent services
Use a compatible provider for PostgreSQL and keep connection strings in secrets. Store user files in object storage and move long-running work into a separate worker where appropriate. This keeps records and uploads independent of the web process that changes when you deploy a new application version.
Test the complete authentication journey
A staging deployment gives you a place to check callbacks, cookies, protected routes, and external service integrations under a real URL. Keep its configuration separate from production. Ship from your agent or GitHub, then use application logs to investigate issues in the deployed service.
A little more detail
Questions about ASP.NET Core?
Does ASP.NET Core require IIS?
No. ASP.NET Core can run on Linux using its application server in an appropriate hosting setup. Your app still needs dependencies that support the selected environment.
Do authentication cookies need special care across releases?
Yes. Review data-protection key persistence and sharing for your application topology. Keys kept only in an ephemeral process or filesystem can cause authentication problems after replacement or across replicas.
From your workspace to the web