fishctl/README.md

109 lines
3.6 KiB
Markdown
Raw Normal View History

2024-07-01 10:22:55 +09:00
# CLI tool for Firefish
2024-06-21 02:09:50 +09:00
## Install and Update
### Install pre-built executable using [cargo-binstall](https://github.com/cargo-bins/cargo-binstall)
```sh
# If you don't have cargo-binstall, install it first
2024-06-21 08:55:11 +09:00
curl -L --proto '=https' --tlsv1.2 -sSf https://raw.githubusercontent.com/cargo-bins/cargo-binstall/main/install-from-binstall-release.sh | bash
2024-06-21 02:09:50 +09:00
# Install pre-built executable
2024-07-01 10:22:55 +09:00
cargo binstall --git https://firefish.dev/firefish/fishctl.git
2024-06-21 02:09:50 +09:00
```
You can update the package using the same command.
```sh
2024-07-01 10:22:55 +09:00
cargo binstall --git https://firefish.dev/firefish/fishctl.git
2024-06-21 02:09:50 +09:00
```
2024-06-21 05:38:43 +09:00
### Download pre-built executable file
2024-07-01 10:22:55 +09:00
You can also download the pre-built executable file from the [release page](https://firefish.dev/firefish/fishctl/-/releases), but you need to manage/update the file on your own.
2024-06-21 05:38:43 +09:00
2024-06-21 02:09:50 +09:00
### Install from source
```sh
# Build from source
2024-07-01 10:22:55 +09:00
cargo install --locked --git https://firefish.dev/firefish/fishctl.git
2024-06-21 02:09:50 +09:00
```
You can update the package using the same command.
```sh
2024-07-01 10:22:55 +09:00
cargo install --locked --git https://firefish.dev/firefish/fishctl.git
2024-06-21 02:09:50 +09:00
```
### Use pre-built OCI image
2024-07-01 10:22:55 +09:00
Using the `registry.firefish.dev/firefish/fishctl` container image, `fishctl ___` commands can be executed as
2024-06-21 02:09:50 +09:00
```sh
2024-07-01 14:09:19 +09:00
# Assuming that $(pwd) (current directory) is the parent of the config directory
# (i.e., the Firefish local repository directory)
2024-06-21 04:54:27 +09:00
docker run -it --rm --volume "$(pwd)":/firefish --network network_name \
2024-07-01 10:22:55 +09:00
registry.firefish.dev/firefish/fishctl \
2024-06-21 02:09:50 +09:00
fishctl ___
# or
2024-06-21 04:54:27 +09:00
podman run -it --rm --volume "$(pwd)":/firefish --network network_name \
2024-07-01 10:22:55 +09:00
registry.firefish.dev/firefish/fishctl \
2024-06-21 02:09:50 +09:00
fishctl ___
```
2024-06-21 08:52:05 +09:00
Where `network_name` is the network name on which the database is running. If you want to use this for the host network (i.e., use the container as if it were a locally installed command), you should replace `network_name` with `host`.
2024-07-01 14:09:19 +09:00
If you are using a container network (which is typically the case if you are using `compose.yml` or `docker-compose.yml` to run Firefish), you need to search for your network name by `docker network ls` or `podman network ls`:
2024-06-21 04:56:49 +09:00
```
$ podman network ls # the network name is `firefish_calcnet` in this case
NETWORK ID NAME DRIVER
0060ac847249 firefish_calcnet bridge
2f259bab93aa podman bridge
```
2024-06-21 02:09:50 +09:00
## Usage
2024-07-01 14:09:19 +09:00
Please make sure to `cd` to the Firefish local repository (more precisely, the parent directory of the config directory) before running these commands, or specify that directory using `--base-dir` option.
If you use a custom Firefish setup and let's say your config files are located at `/etc/firefish/config`, you should provide `--base-dir /etc/firefish` option or `cd` to `/etc/firefish` directory.
2024-06-21 02:09:50 +09:00
2024-06-21 05:00:46 +09:00
### Update the config files
2024-06-21 02:09:50 +09:00
[The admin note](https://firefish.dev/firefish/firefish/-/blob/main/docs/notice-for-admins.md) may tell you that you need to update the config files. In such a case, please execute the following command.
```sh
2024-06-21 05:00:46 +09:00
fishctl config update
2024-06-21 02:09:50 +09:00
```
2024-06-21 14:12:59 +09:00
You can also specify the revision to update to, but this feature is for development purposes only.
```sh
fishctl config update v1
```
2024-06-21 02:09:50 +09:00
### Validate the config files
2024-06-21 13:16:16 +09:00
Execute the following command to validate the config files.
2024-06-21 02:09:50 +09:00
```sh
fishctl config validate
```
2024-06-21 13:16:16 +09:00
2024-07-01 14:09:19 +09:00
Please note that some items are only formally checked. Even if the output says it is valid, your settings can be incorrect.
2024-06-25 11:59:42 +09:00
2024-07-01 14:09:19 +09:00
This command performs a connection check against the PostgreSQL server and the cache server (Valkey/Redis). You can bypass this check using the `--offline` option:
2024-06-25 12:25:35 +09:00
```sh
fishctl config validate --offline
```
2024-06-25 11:59:42 +09:00
### Generate VAPID keys for push notifications
```sh
fishctl generate vapid
```