AkkomaGang/akkoma
AkkomaGang/akkoma
15
65
Fork 92
Code Issues 177 Pull requests 25 Projects 2 Releases 14 Packages Wiki Activity

Improve styling of CLI tasks

Browse source
This commit is contained in:
rinpatch 2019-10-03 08:51:57 +03:00
parent 869ea2ab90
commit a54739a530
2 changed files with 8 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/administration/CLI_tasks/digest.md
View file

@ -1,14 +1,12 @@
# Managing digest emails # Managing digest emails
Every command should be ran with a prefix, in case of OTP releases it is `./bin/pleroma_ctl digest` and in case of source installs it's `mix pleroma.digest`. Every command should be ran with a prefix, in case of OTP releases it is `./bin/pleroma_ctl digest` and in case of source installs it's `mix pleroma.digest`.
## `test` ## Send digest email since given date (user registration date by default) ignoring user activity status.
```sh ```sh
$PREFIX test <nickname> <since_date> $PREFIX test <nickname> [<since_date>]
``` ```
Send digest email since given date (user registration date by default) ignoring user activity status.
Example: Example:
```sh ```sh
$PREFIX test donaldtheduck 2019-05-20 $PREFIX test donaldtheduck 2019-05-20

15
docs/administration/CLI_tasks/emoji.md
View file

@ -2,31 +2,28 @@
Every command should be ran with a prefix, in case of OTP releases it is `./bin/pleroma_ctl emoji` and in case of source installs it's `mix pleroma.emoji`. Every command should be ran with a prefix, in case of OTP releases it is `./bin/pleroma_ctl emoji` and in case of source installs it's `mix pleroma.emoji`.
## `ls-packs` ## Lists the emoji packs and metadata specified in the manifest.
```sh ```sh
$PREFIX ls-packs [OPTION...] $PREFIX ls-packs [<options>]
``` ```
Lists the emoji packs and metadata specified in the manifest.
### Options ### Options
- `-m, --manifest PATH/URL` - path to a custom manifest, it can either be an URL starting with `http`, in that case the manifest will be fetched from that address, or a local path - `-m, --manifest PATH/URL` - path to a custom manifest, it can either be an URL starting with `http`, in that case the manifest will be fetched from that address, or a local path
## `get-packs` ## Fetch, verify and install the specified packs from the manifest into `STATIC-DIR/emoji/PACK-NAME`
```sh ```sh
$PREFIX get-packs [OPTION...] PACKS $PREFIX get-packs [<options>] <packs>
``` ```
Fetches, verifies and installs the specified PACKS from the manifest into the `STATIC-DIR/emoji/PACK-NAME`
### Options ### Options
- `-m, --manifest PATH/URL` - same as [`ls-packs`](#ls-packs) - `-m, --manifest PATH/URL` - same as [`ls-packs`](#ls-packs)
## `gen-pack` ## Create a new manifest entry and a file list from the specified remote pack file
```sh ```sh
$PREFIX gen-pack PACK-URL $PREFIX gen-pack PACK-URL
``` ```
Creates a new manifest entry and a file list from the specified remote pack file. Currently, only .zip archives are recognized as remote pack files and packs are therefore assumed to be zip archives. This command is intended to run interactively and will first ask you some basic questions about the pack, then download the remote file and generate an SHA256 checksum for it, then generate an emoji file list for you. Currently, only .zip archives are recognized as remote pack files and packs are therefore assumed to be zip archives. This command is intended to run interactively and will first ask you some basic questions about the pack, then download the remote file and generate an SHA256 checksum for it, then generate an emoji file list for you.
The manifest entry will either be written to a newly created `index.json` file or appended to the existing one, *replacing* the old pack with the same name if it was in the file previously. The manifest entry will either be written to a newly created `index.json` file or appended to the existing one, *replacing* the old pack with the same name if it was in the file previously.