recaptime.dev / phorge
@recaptime-dev's working patches + fork for Phorge, a community fork of Phabricator. (Upstream dev and stable branches are at upstream/main and upstream/stable respectively.) hq.recaptime.dev/wiki/Phorge
phorge phabricator
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

docs: fix setup instructions for Mailgun and S3

Summary: The S3 fields are mandatory and if you only enter the ones in the docs you will immediately encounter a "Amazon S3 is Only Partially Configured" error. For Mailgun the error is more difficult to figure out - emails get stuck on Mailgun's side but the error is illegible. On Phabricator's side you have to go trawling through nginx logs to find "Mail signature is not valid. Check your Mailgun API key."

Test Plan: Deploy a new standalone instance, follow old instructions, fail. Deploy another one, follow updated instructions, win.

Reviewers: epriestley, #blessed_reviewers

Reviewed By: epriestley, #blessed_reviewers

Subscribers: Korvin

Differential Revision: https://secure.phabricator.com/D15931

Luka Kladaric 174f3f6d bf543721

+3
+2
src/docs/user/configuration/configuring_file_storage.diviner
··· 164 164 165 165 - `amazon-s3.access-key`: Your AWS access key. 166 166 - `amazon-s3.secret-key`: Your AWS secret key. 167 + - `amazon-s3.region`: Your AWS S3 region. 168 + - `amazon-s3.endpoint`: Your AWS S3 endpoint. 167 169 - `storage.s3.bucket`: S3 bucket name where files should be stored. 168 170 169 171 Testing Storage Engines
+1
src/docs/user/configuration/configuring_inbound_email.diviner
··· 128 128 - Add a Mailgun route with a `catch_all()` rule which takes the action 129 129 `forward("https://phabricator.example.com/mail/mailgun/")`. Replace the 130 130 example domain with your actual domain. 131 + - Set the `mailgun.api-key` config key to your Mailgun API key. 131 132 132 133 = SendGrid Setup = 133 134