diff options
author | rinpatch <rinpatch@sdf.org> | 2018-12-20 11:29:08 +0300 |
---|---|---|
committer | rinpatch <rinpatch@sdf.org> | 2018-12-20 11:29:08 +0300 |
commit | acfd98689bcd6bb955553117f1e702cbf7577925 (patch) | |
tree | 83d6e6a3a59718cb0646f8caec9f4ccf184aa3ae | |
parent | 6081c44961f17561b885beb18478fba57b7db101 (diff) | |
download | pleroma-acfd98689bcd6bb955553117f1e702cbf7577925.tar.gz |
Fix config.md path in README
-rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -39,7 +39,7 @@ While we don't provide docker files, other people have written very good ones. T * Run `mix pleroma.instance gen`. This will ask you 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`. It will also create a `config/setup_db.psql`, which you should run as the PostgreSQL superuser (i.e., `sudo -u postgres psql -f config/setup_db.psql`). It will create the database, user, and password you gave `mix pleroma.gen.instance` earlier, as well as set up the necessary extensions in the database. PostgreSQL superuser privileges are only needed for this step. - * For these next steps, the default will be to run pleroma using the dev configuration file, `config/dev.secret.exs`. To run them using the prod config file, prefix each command at the shell with `MIX_ENV=prod`. For example: `MIX_ENV=prod mix phx.server`. Documentation for the config can be found at [``config/config.md``](docs/config.md) + * For these next steps, the default will be to run pleroma using the dev configuration file, `config/dev.secret.exs`. To run them using the prod config file, prefix each command at the shell with `MIX_ENV=prod`. For example: `MIX_ENV=prod mix phx.server`. Documentation for the config can be found at [``docs/config.md``](docs/config.md) * Run `mix ecto.migrate` to run the database migrations. You will have to do this again after certain updates. |