summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPartial name <partial.ice9@protonmail.com>2017-11-25 02:42:39 +0000
committerPartial name <partial.ice9@protonmail.com>2017-11-25 02:42:39 +0000
commitf86fca682a1a4ca71169003b714cc3ad104c411d (patch)
tree3ebd4168d28de0abb3573825f50047d320ac2f17
parent44f7154fb97f29ae519afb8581c4379674c9f574 (diff)
downloadpleroma-f86fca682a1a4ca71169003b714cc3ad104c411d.tar.gz
pleroma-f86fca682a1a4ca71169003b714cc3ad104c411d.zip
fix mix typo in README.md
$ mix phx.serve ** (Mix) The task "phx.serve" could not be found. Did you mean "phx.server"? $ mix phx.server [info] Running Pleroma.Web.Endpoint with Cowboy using http://0.0.0.0:4000
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 5fd08e2f2..b07593f67 100644
--- 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.