fix typos
This commit is contained in:
committed by
Umputun
parent
98bfc7f5f5
commit
2b15e9291f
+4
-4
@@ -10,14 +10,14 @@ This documentation describes how to enable the email-related capabilities of Rem
|
||||
|
||||
enabling this will let the user log in using their emails:
|
||||
|
||||

|
||||

|
||||
|
||||
- email notifications for any users except anonymous:
|
||||
|
||||
GitHub or Google or Twitter or any other kind of user gets the ability to get
|
||||
email notifications about new replies to their comments (and any of the replies down the tree):
|
||||
|
||||

|
||||

|
||||
|
||||
## Setup email server connection
|
||||
|
||||
@@ -51,7 +51,7 @@ This is an example of a configuration using [Mailgun](https://www.mailgun.com/)
|
||||
|
||||
When you don't want to expose your IP (which is impossible with any SMTP provider)
|
||||
and for situations when connecting to external SMTP server is impossible due to firewall
|
||||
settings is setting up an SMTP-to-API bridge and sending messages trough it.
|
||||
settings is setting up an SMTP-to-API bridge and sending messages through it.
|
||||
|
||||
To use any of containers below with in remark42 environment set following two `SMTP` variables:
|
||||
|
||||
@@ -104,7 +104,7 @@ This is an example of a configuration using [SendGrid](https://sendgrid.com/) em
|
||||
|
||||
When you don't want to expose your IP (which is impossible with any SMTP provider)
|
||||
and for situations when connecting to external SMTP server is impossible due to firewall
|
||||
settings is setting up an SMTP-to-API bridge and sending messages trough it.
|
||||
settings is setting up an SMTP-to-API bridge and sending messages through it.
|
||||
|
||||
To use any of containers below with in remark42 environment set following two `SMTP` variables:
|
||||
|
||||
|
||||
+1
-1
@@ -88,7 +88,7 @@ spec:
|
||||
cpu: "1"
|
||||
memory: "1Gi"
|
||||
securityContext:
|
||||
# Has its own root priviledge drop. Can't do runAsUser / runAsGroup.
|
||||
# Has its own root privilege drop. Can't do runAsUser / runAsGroup.
|
||||
volumes:
|
||||
- name: srvvar
|
||||
persistentVolumeClaim:
|
||||
|
||||
+1
-1
@@ -51,4 +51,4 @@ server {
|
||||
}
|
||||
```
|
||||
|
||||
note: `proxy_pass` points to internal DNS name `remark42` and expected to run from the same compose. If nginx runs outside of compose the real IP (or docker's bridge IP) should be used
|
||||
note: `proxy_pass` points to internal DNS name `remark42` and expected to run from the same compose. If nginx runs outside compose the real IP (or docker's bridge IP) should be used
|
||||
|
||||
+2
-2
@@ -2,9 +2,9 @@
|
||||
title: Reproxy
|
||||
---
|
||||
|
||||
## How to configure remark42 with [reproxy](https://reproxy.io)
|
||||
## How to configure remark42 with [Reproxy](https://reproxy.io)
|
||||
|
||||
Example of reproxy configuration (reverse proxy) running remark42 service on remark42.example.com with docker compose. Reproxy handles SSL termination with LE and gzip all the responses.
|
||||
Example of Reproxy configuration (reverse proxy) running remark42 service on remark42.example.com with docker compose. Reproxy handles SSL termination with LE and gzip all the responses.
|
||||
|
||||
```yaml
|
||||
version: "3.4"
|
||||
|
||||
+2
-2
@@ -20,7 +20,7 @@ In order to integrate notifications from remark42 with the [slack](https://slack
|
||||
|
||||
The slack token which you obtained before should be used as `NOTIFY_SLACK_TOKEN`.
|
||||
|
||||
You also need to set `NOTIFY_ADMINS=slack` for the slack notification to be active.
|
||||
You also need to set `NOTIFY_ADMINS=slack` for the Slack notification to be active.
|
||||
|
||||
By default, the notification are sent to the `general` channel on slack. If you need another channel, you can specify it, for instance with `NOTIFY_SLACK_CHAN=random`.
|
||||
|
||||
@@ -33,7 +33,7 @@ By default, the notification are sent to the `general` channel on slack. If you
|
||||
|
||||
### Verify the notifications on Slack
|
||||
|
||||
If all goes fine, you should be able to see the following message on your slack notification channel:
|
||||
If all goes fine, you should be able to see the following message on your Slack notification channel:
|
||||
|
||||
> New comment from _author_ -> _original author_
|
||||
>> [Demo | Remark42](http://127.0.0.1:8080/web/#remark42__comment-11288987987)
|
||||
|
||||
+1
-1
@@ -25,7 +25,7 @@ Originally tested on [Nuxt.js](https://nuxtjs.org/), but it should be applicable
|
||||
})
|
||||
```
|
||||
|
||||
- Created `remark42Instance` when the `div` containing remark42 has appear, usually at `mounted` or `componentDidMount` of the SPA lifecycle. Destroy the previous instance first, if neccessary.
|
||||
- Created `remark42Instance` when the `div` containing remark42 has appeared, usually at `mounted` or `componentDidMount` of the SPA lifecycle. Destroy the previous instance first, if necessary.
|
||||
|
||||
```ts
|
||||
initRemark42() {
|
||||
|
||||
Reference in New Issue
Block a user