Run a Porter Instance
Last updated
Last updated
By default, Porter runs over HTTP. However, Porter instances must be secured with a valid HTTPS certificate in order to be compatible with network applications. A Porter instance running without SSL/TLS is not only insecure but also browser-based apps and websites will be unable to connect.
To secure your Docker-run Porter instance with HTTPS, use a reverse proxy like or for SSL processing, and potentially for automated SSL certificate issuance and renewal. Additionally, consider using cloud-based services like AWS/Digital Ocean load balancers or Cloudflare for SSL termination and enhanced security.
HTTPS: To run the Porter service over HTTPS, it will require a TLS key and a TLS certificate.
CORS: Allowed origins for
Authentication: Optional usage restriction (non-public instance) via authentication protocols, e.g. basic authentication, etc. if desired
Get the latest porter
image
Run Porter HTTP Service on port 80
The command above is for illustrative purposes and can be modified as necessary.
Porter will be available on default port 80 (HTTP)
View Porter logs
Stop Porter service
View the for more information.