systemd after redis

[metebalci]

I am not 100% sure but I think start by systemd scripts may fail because redis may not have started (not sure if initial redis connection must be present but I experienced a startup problem). So a solution can be to add After=redis.service to systemd scripts or to mention this as a comment or in documents.

[thystra]

FYI from a downstream maintainer: the native Debian package in
thystra/Activity-Relay installs a
dedicated activity-relay-redis.service.

Both the API server and worker units declare
Requires=activity-relay-redis.service and
After=network-online.target activity-relay-redis.service, and they restart
on failure. This addresses the Redis startup-ordering concern for the packaged
deployment.

The implementation is included in stable
v2.5.0.
This is a downstream implementation, not a claim that it has been merged
upstream.