logo

pleroma

My custom branche(s) on git.pleroma.social/pleroma/pleroma
commit: ecf109a0fe65c0221a2d9077156fb4af322f847a
parent: 44dc6948823f5e26ede427d3348fef72129f3f4d
Author: Lain Iwakura <lain@soykaf.club>
Date:   Thu, 23 Nov 2017 16:35:03 +0100

Add mix deps.get back to readme.

Diffstat:

MREADME.md2++
1 file changed, 2 insertions(+), 0 deletions(-)

diff --git a/README.md b/README.md @@ -27,6 +27,8 @@ No release has been made yet, but several servers have been online for months al ### Configuration + * Run `mix deps.get` to install elixir dependencies. + * Run `mix generate_config`. This will ask you a few questions about your instance and generate a configuration file in `config/generated_config.exs`. Check that and copy it to either `config/dev.secret.exs` or `config/prod.secret.exs`. 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. * 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/