From f085171daa27e87367086c045960fdff2e6392ec Mon Sep 17 00:00:00 2001 From: sn0w Date: Sat, 18 Aug 2018 23:32:33 +0200 Subject: [PATCH] Add note about maintenance --- README.md | 8 +++++++- pleroma | 2 +- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index dbb3169..0d24065 100644 --- a/README.md +++ b/README.md @@ -59,6 +59,12 @@ Every time you run `./pleroma build` the script will fetch all upstream changes This means that setting `PLEROMA_VERSION` to a branch enables rolling-release updates while setting it to a tag or commit-hash pins the version. +## Maintaining Pleroma + +Pleroma maintenance is usually done with premade mix tasks. +You can run these tasks using `./pleroma mix [task] [arguments...]`. +If you need to fix some bigger issues you can also spawn a shell using `./pleroma enter`. + ## Customizing Pleroma Just add your customizations (and their folder structure) to `custom.d`.
@@ -182,4 +188,4 @@ ssl_certificate /ssl/ssl.crt; ssl_certificate_key /ssl/ssl.key; ``` -In traefik-mode and manual-mode these files and the `SCRIPT_LOCAL_SSL` value are ignored. +In traefik-mode and manual-mode these files and the `SCRIPT_ENABLE_SSL` value are ignored. diff --git a/pleroma b/pleroma index 9cbca0b..783a839 100755 --- a/pleroma +++ b/pleroma @@ -80,7 +80,7 @@ load_env() { action__build() { docker_compose build --build-arg __BUST_CACHE="$(date +%s)" server; } action__debug() { render_template; } action__down() { action__stop; } -action__enter() { docker_compose exec server ash; } +action__enter() { docker_compose exec server ash -c 'cd /pleroma && ash'; } action__lint() { render_template | jq; } action__logs() { docker_compose logs -f; } action__mix() { docker_compose exec server ash -c "cd /pleroma && mix $*"; }