Infrastructure
  1. Infrastructure
  2. INFRA-6066

Configuring email on allura-vm.apache.org

    Details

    • Type: Task Task
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Later
    • Fix Version/s: Initial Clearing
    • Component/s: VMWare
    • Labels:
      None
    • Environment:
      Ubuntu 12.04.2 LTS

      Description

      We've got a copy of our project (Allura) running on our VM onder mod_wsgi. The next step of our setup is to get email working. Our app needs to be able to send outbound email. We also have a custom python smtp server for handling inbound email to the app (port is configurable).

      Wanted to check with you guys first before tinkering with this myself. How should I proceed? Thanks!

        Activity

        Hide
        Gavin added a comment -
        This is a demo, what is the email usage for please? Outbound to where?
        Show
        Gavin added a comment - This is a demo, what is the email usage for please? Outbound to where?
        Hide
        Tim Van Steenburgh added a comment -
        Sorry for the delay, I totally missed that this ticket was commented on.

        In short, this is not a demo. We are planning to move all of our daily development to the Apache hosted Allura instance. Our instance will also serve as a proof-of-concept for other projects which may wish to use Allura for their development in the future.

        Inbound email is parsed and used to automatically updated discussions on tickets and other artifacts. Outbound email is for sending notifications to subscribed users when tickets and other artifacts are updated.

        Thanks for your help!
        Show
        Tim Van Steenburgh added a comment - Sorry for the delay, I totally missed that this ticket was commented on. In short, this is not a demo. We are planning to move all of our daily development to the Apache hosted Allura instance. Our instance will also serve as a proof-of-concept for other projects which may wish to use Allura for their development in the future. Inbound email is parsed and used to automatically updated discussions on tickets and other artifacts. Outbound email is for sending notifications to subscribed users when tickets and other artifacts are updated. Thanks for your help!
        Hide
        Gavin added a comment -
        What are your plans for the scm integration component ?
        (Also no accts should be created until this non-demo is SSLd)
        Show
        Gavin added a comment - What are your plans for the scm integration component ? (Also no accts should be created until this non-demo is SSLd)
        Hide
        Tim Van Steenburgh added a comment -
        For scm integration we just need filesystem access (read) to the allura git repo. An NFS mount would be fine. More discussion here: https://issues.apache.org/jira/browse/INFRA-5064

        How do we proceed with getting SSL set up?
        Show
        Tim Van Steenburgh added a comment - For scm integration we just need filesystem access (read) to the allura git repo. An NFS mount would be fine. More discussion here: https://issues.apache.org/jira/browse/INFRA-5064 How do we proceed with getting SSL set up?
        Hide
        #asfinfra Bot added a comment -
        <danielsh> Back a step please. If you'd like to use something other than {svn,git-wip-us}.a.o, please start a thread. We need to see how things like committers authn, backups, members supervision (if you have private lists/forums) work.
        Show
        #asfinfra Bot added a comment - <danielsh> Back a step please. If you'd like to use something other than {svn,git-wip-us}.a.o, please start a thread. We need to see how things like committers authn, backups, members supervision (if you have private lists/forums) work.
        Hide
        Dave Brondsema added a comment -
        We use git-wip-us.a.o and aren't planning on changing that at all. We just want to have readonly access to that so that we can show commits, index metadata, etc.

        I don't think we're planning on any private forums or content, but it is possible we would in the future. Backups is something we should discuss -- which mailing list is appropriate?
        Show
        Dave Brondsema added a comment - We use git-wip-us.a.o and aren't planning on changing that at all. We just want to have readonly access to that so that we can show commits, index metadata, etc. I don't think we're planning on any private forums or content, but it is possible we would in the future. Backups is something we should discuss -- which mailing list is appropriate?
        Hide
        #asfinfra Bot added a comment -
        <danielsh> Backups of what? Issue tracker data? Anyway, infra@ is a fine place to start (we might move it to infra-p@ later)
        Show
        #asfinfra Bot added a comment - <danielsh> Backups of what? Issue tracker data? Anyway, infra@ is a fine place to start (we might move it to infra-p@ later)
        Hide
        #asfinfra Bot added a comment -
        <danielsh> Feedback timeout. Please reopen and address our comments above asking you to take an action or answer a question.
        Show
        #asfinfra Bot added a comment - <danielsh> Feedback timeout. Please reopen and address our comments above asking you to take an action or answer a question.

          People

          • Assignee:
            Unassigned
            Reporter:
            Tim Van Steenburgh
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development