coreos-home-server/service/redis
Alex Palaistras 0fbbc39e27 base: Only copy service directories if used
We no longer copy service directories into `/etc/coreos-home-server` if
these have not had their respective `spec.bu` files included; these
directories are not needed in these cases, and would be erroneously
considered as eligible in subsequent `coreos-home-server-update`
invocations.
2022-02-05 16:05:00 +00:00
..
container/config Flatten directory structures 2022-01-15 11:43:33 +00:00
systemd Flatten directory structures 2022-01-15 11:43:33 +00:00
Containerfile Flatten directory structures 2022-01-15 11:43:33 +00:00
README.md Flatten directory structures 2022-01-15 11:43:33 +00:00
spec.bu base: Only copy service directories if used 2022-02-05 16:05:00 +00:00

Redis

This directory contains a simple systemd service for running a disk-backed instance of Redis.

Deployment

Including the spec.bu file here in your host configuration is enough to have Redis enabled on the system -- no other configuration is needed. The following commands will manage the service accordingly:

  • Starting Redis: sudo systemctl start redis
  • Stopping Redis: sudo systemctl stop redis
  • Getting logs for the running service: journalctl -feu redis

By default, Redis listens on the internal network under the redis hostname, port 6379. Any services that wish to connect to Redis for that hostname and port need to also be included in the internal network.

By default, a named volume is created for redis which is used for restoring databases on service restart.

Use

Depending on Redis from other systemd services is as simple as declaring an ordered dependency in the systemd service file, for example:

[Unit]
Description=Service That Uses Redis
Wants=container-build@example.service redis.service
After=container-build@example.service redis.service

Redis will then be guaranteed to be running before the example service is.