# Overview
In general, to deploy SSCMS to a hosting environment:
- Deploy the downloaded SSCMS files to a folder on the hosting server.
- Set up a process manager and reverse proxy.
# Publish to a folder
A .NET Core app can be published as self-contained deployment or framework-dependent deployment. SSCMS is self-contained, the assembly files that contain the .NET runtime are included in the publish folder.
# Set up a process manager and reverse proxy
SSCMS is a console app that must be started when a server boots and restarted if it crashes.
The reverse proxy server receives HTTP requests from the network and forwards them to the SSCMS.
SSCMS communicates directly with the Internet without using a reverse proxy server:
SSCMS communicates indirectly with the Internet through a reverse proxy server such as IIS, Nginx, or Apache:
With a reverse proxy, you also get the following benefits:
- Can limit the exposed public surface area of the apps that it hosts.
- Provide an additional layer of configuration and defense.
- Might integrate better with existing infrastructure.
- Simplify load balancing and secure communication (HTTPS) configuration. Only the reverse proxy server requires an X.509 certificate, and that server can communicate with the app's servers on the internal network using plain HTTP.
NOTE
A reverse proxy is required to deploy SSCMS in a formal environment.
To automate starts and restarts, a process manager and reverse proxy is required. The most common process managers for ASP.NET Core are: