a6d84190eb
This setup is a way to manage workers with systemd. It does however not require workers. You can use this setup without workers. You just have to make sure that the homeserver is forking and writes its PID file to the location the service is looking in. The currently distributed setup in the debian package does not work in conjunction with workers. * Adds changelog * Lets systemd handle the forking Sets all services to `type=simple` and disables daemonizing on the synapse side. * Formats readme to 80 columns per line * Allows for full restart of all workers * Changes README to reflect the new setup * Adds dot to end of changelog file * Removes surplus word Co-Authored-By: targodan <targodan@users.noreply.github.com> * Adds missing word Co-Authored-By: targodan <targodan@users.noreply.github.com> * Fixes linebreak Co-Authored-By: targodan <targodan@users.noreply.github.com> * Fixes unit type |
||
|---|---|---|
| .. | ||
| cmdclient | ||
| docker | ||
| experiments | ||
| grafana | ||
| graph | ||
| jitsimeetbridge | ||
| prometheus | ||
| purge_api | ||
| scripts | ||
| systemd | ||
| systemd-with-workers | ||
| vertobot | ||
| README.rst | ||
| example_log_config.yaml | ||
README.rst
Community Contributions ======================= Everything in this directory are projects submitted by the community that may be useful to others. As such, the project maintainers cannot guarantee support, stability or backwards compatibility of these projects. Files in this directory should *not* be relied on directly, as they may not continue to work or exist in future. If you wish to use any of these files then they should be copied to avoid them breaking from underneath you.