commit: 89a8dc748525063afc673e49875d0b605df73d77
parent: 44f7154fb97f29ae519afb8581c4379674c9f574
Author: eal <eal@waifu.club>
Date: Sat, 25 Nov 2017 23:10:43 +0000
Merge branch 'patch-1' into 'develop'
fix mix typo in README.md
See merge request pleroma/pleroma!31
Diffstat:
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.md b/README.md
@@ -35,7 +35,7 @@ No release has been made yet, but several servers have been online for months al
* Run `mix ecto.migrate` to run the database migrations. You will have to do this again after certain updates.
- * You can check if your instance is configured correctly by running it with `mix phx.serve` and checking the instance info endpoint at `/api/v1/instance`. If it shows your uri, name and email correctly, you are configured correctly. If it shows something like `localhost:4000`, your configuration is probably wrong, unless you are running a local development setup.
+ * You can check if your instance is configured correctly by running it with `mix phx.server` and checking the instance info endpoint at `/api/v1/instance`. If it shows your uri, name and email correctly, you are configured correctly. If it shows something like `localhost:4000`, your configuration is probably wrong, unless you are running a local development setup.
* The common and convenient way for adding HTTPS is by using Nginx as a reverse proxy. You can look at example Nginx configuration in `installation/pleroma.nginx`. If you need TLS/SSL certificates for HTTPS, you can look get some for free with letsencrypt: https://letsencrypt.org/
On Debian you can use `certbot` package and command to manage letsencrypt certificates.