There is a header describing `data-isso-reply-notifications` but it is not in the initial data attributes examples. I assume the initial list is meant to be exhaustive? I overlooked this setting on my initial read through the docs because it wasn't there, so I thought it would be helpful to add.
Merging @pellenilsson reply notification PR
* Added reply notification for commenter
* Removed debug info
* Bugfix
* Add notification column to database if needed
* Make SMTP connections thread safe
* Include link to comment in email notifications
* Implement opt-out for email notifications
* Fix faulty check for parent comment
* Support notifications also for replies
* Don't send notification when someone responds to his/her own comment
* Make unsubscribe work with notifications for replies
* Correct hash in 'unsubscribe' API example
* Introduce public-endpoint setting
* Fix whitespace issue
* Postpone notifications to users until comment has been approved by moderator
* New setting general.reply-notifications
* Add client-side configuration setting reply-notifications
* Documentation for reply notifications
On server-side, this can be enabled by providing a base URL to use to
build the full URL. Limit also becomes configurable. On client-side,
we need to add a switch to know whatever or not the additional link
can be displayed.
Many of the Docker images on hub.docker.com are outdated. The one
specified in the documentation doesn't exist anymore. We provide a
decent Dockerfile to build our own Docker image.
This uses a multi-stage build to avoid polluting the final image with
the intermediate artifacts. The final image is 155 MB. It should be
possible to squeeze it even more by using Alpine Linux for the last
two parts instead of Stretch.
The service is using gunicorn. The user is expected to complete the
installation with a reverse proxy configuration.
