Describe the conductor controller

1 files changed, 11 insertions, 0 deletions

diff --git a/README.md b/README.md
index 578d12abee..db55cf197b 100644
--- a/README.md
+++ b/README.md
@@ -8,10 +8,12 @@ The inbound emails are turned into `InboundEmail` records using Active Record an
 
 These inbound emails are routed asynchronously using Active Job to one or several dedicated mailboxes, which are capable of interacting directly with the rest of your domain model.
 
+
 ## How does this compare to Action Mailer's inbound processing?
 
 Rails has long had an anemic way of [receiving emails using Action Mailer](https://guides.rubyonrails.org/action_mailer_basics.html#receiving-emails), but it was poorly flushed out, lacked cohesion with the task of sending emails, and offered no help on integrating with popular inbound email processing platforms. Action Mailbox supersedes the receiving part of Action Mailer, which will be deprecated in due course.
 
+
 ## Installing
 
 Assumes a Rails 5.2+ application:
@@ -30,6 +32,10 @@ Assumes a Rails 5.2+ application:
    ./bin/rails db:migrate
    ```
 
+## Configure ingress path and password
+
+TODO
+
 ## Examples
 
 Configure basic routing:
@@ -84,6 +90,11 @@ end
 ```
 
 
+## Create incoming email through a conductor module in development
+
+It's helpful to be able to test incoming emails in development without actually sending and receiving real emails. To accomplish this, there's a conductor controller mounted at `/rails/conductor/action_mailbox/inbound_emails`, which gives you an index of all the InboundEmails in the system, their state of processing, and a form to create a new InboundEmail as well.
+
+
 ## Development road map
 
 Action Mailbox is destined for inclusion in Rails 6, which is due to be released some time in 2019. We will refine the framework in this separate rails/actionmailbox repository until we're ready to promote it via a pull request to rails/rails.