LeadMagnet/leadchat
1
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity

Chore: Moved the email ingress method to an env variable (#777) (#806)

Browse Source 
* Chore: Moved the email ingress method to an env variable (#777)
* Moved the email ingress method in config to an environment variable
* Updated documentation to reflect this

* Added ingress config to staging env config (#777)
* Re-arranged the order in env configs so that email related configs are together
This commit is contained in:
Sony Mathew
2020-05-02 23:29:09 +05:30
committed by GitHub
parent 8655466fa5
commit d8131e450c
5 changed files with 46 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/development/project-setup/conversation-continuity.md
View File

@@ -19,16 +19,16 @@ With a second step that we have done, we are now introducing the capability of c
There are a couple of email infrastructure service providers to handle the incoming emails that we support at the moment. They are
Sendgrid, Mandrill, Mailgun, Exim, Postfix, Qmail and Postmark.
Step 1 : We have to set the ingress option in `config/environments/production.rb`.
Step 1 : We have to set the inbound email service used as an environment variable.
```bash
# Set this to appropriate ingress service for which the options are :
# :relay for Exim, Postfix, Qmail
# :mailgun for Mailgun
# :mandrill for Mandrill
# :postmark for Postmark
# :sendgrid for Sendgrid
config.action_mailbox.ingress = :sendgrid
# "relay" for Exim, Postfix, Qmail
# "mailgun" for Mailgun
# "mandrill" for Mandrill
# "postmark" for Postmark
# "sendgrid" for Sendgrid
RAILS_INBOUND_EMAIL_SERVICE=relay
```
This configures the ingress service for the app. Now we have to set the password for the ingress service that we use.