From ac3c2391e8579f9141f5101b6ebb91c9c1d0ba04 Mon Sep 17 00:00:00 2001 From: Alex Kern Date: Wed, 25 Dec 2019 19:25:54 -0800 Subject: [PATCH] Update README --- README.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/README.md b/README.md index 41bfa72..32e600c 100644 --- a/README.md +++ b/README.md @@ -13,11 +13,7 @@ A hosted instance of FilePizza is available at [file.pizza](https://file.pizza). ## Installation -The recommended way to deploy FilePizza is as a [Docker container](https://hub.docker.com/r/kern/filepizza). - - $ docker run -p 8080:8080 -e PORT=8080 -it kern/filepizza:master - -WebRTC only works over HTTPS, so you'll either have to get a signed HTTPS key/certificate from a CA such as [Let's Encrypt](https://letsencrypt.org/getting-started/)) or generate your own [self-signed pair](https://devcenter.heroku.com/articles/ssl-certificate-self) and trust it. Then, to run FilePizza with HTTPS termination: +The recommended way to deploy FilePizza is as a [Docker container](https://hub.docker.com/r/kern/filepizza). WebRTC only works over HTTPS, so you'll either have to get a signed HTTPS key/certificate from a CA such as [Let's Encrypt](https://letsencrypt.org/getting-started/)) or generate your own [self-signed pair](https://devcenter.heroku.com/articles/ssl-certificate-self) and trust it. Then, to run FilePizza (with HTTPS termination): $ docker run \ -p 8080:8080 -e PORT=8080 \