Make WordPress Systems

Updates from December, 2014 Toggle Comment Threads | Keyboard Shortcuts

  • Andrew Nacin 5:26 am on December 16, 2014 Permalink |  

    Moving the NFS mounts 

    Per a conversation with @barry, we’re going to move most NFS mounts on .org to a single centralized location. Here’s the checklist, in order:

    After that:

  • Jen 9:01 pm on November 18, 2014 Permalink |
    Tags: , gmail   

    Email & Google Apps 

    We have a handful of @wordpress.org email addresses set up as forwards. For the teams that need an official email address and a supportpress/supportflow setup, we have been doing addresses on wordcamp.org (which has mailboxes) or setting up one-off gmail addresses to handle the mailbox, the owner of which might get lost over time. I talked to Barry at the team meetup days at WCSF about this and he said we should put wordpress.org on gmail for email. Matt said this was okay.

    I’ve reclaimed the Foundation account for google apps for non-profits (a WC organizer had used the tax id to claim it without asking first, so we had to jump through some hoops). I’ve set up the account and gone through the steps with Ashish Shukla to have it recognize wordpress.org as the domain. The next step would be to modify the MX record to start routing email through the google apps account, but that gets complicated when it comes to ensuring no disruption to existing forwards, which is why Ashish and I were waiting for Barry to be available. When I spoke to Barry today, he said that @nacin is doing something around email too, so now he’s not super comfortable making changes at all lest we inadvertently step on each others’ toes.

    @nacin: what is the thing you are doing with email, and does it preclude a shift to having actual mailboxes that are official? Let’s coordinate with whomever else is working on this to make sure everyone’s needs are met. I’m happy to share the google credentials with the appropriate people to get it going. We also get stuff like official hangouts the teams can use, calendar, etc. as part of the google apps account. If there’s a reason *not* to take Barry’s advice about using google apps/gmail for the team emails, I can remove wordpress.org from the google account (if so, please explain).

    • Andrew Nacin 11:02 pm on November 18, 2014 Permalink | Log in to Reply

      Hey @jenmylo, I’m trying to figure out the exact use case for doing this. We’ve always done forwards, which works perfectly well for these two situations:

      • An individual person who needs their mail forwarded to their primary email
      • A group email that needs to be forwarded to multiple people

      Google Apps would add overhead to both of these.

      Then there’s the third use case, which is a “mailbox.” Even if we switched to Google Apps, we wouldn’t actually have people accessing these mailboxes directly. We would pipe emails through a SupportPress or Supportflow install. The only benefit to this setup, thus, would be replacing this procedure: “setting up one-off gmail addresses to handle the mailbox, the owner of which might get lost over time”.

      Yes, this is indeed our current approach. But it actually works quite well. I know of eight such accounts in use, and all of the passwords are stored in a single configuration location. I’m not sure about the missing owner situation — perhaps it has happened before, but in order for SupportPress/Supportflow to actually connect to these accounts, it needs the password anyway, which ultimately controls everything for these. Even if we moved to Google Apps, we’d still need a similar configuration.

      I remember talking to Barry about this at WCSF and at the time at least, we both thought this was about WordCamp.org moving to Google Apps. I don’t know what the requirements are there (with regards to organizing teams and how that all works), and I have no opinion either way on which direction WordCamp.org is set up. With WordPress.org, I don’t see the reason for switching.

      I’ve been dealing with a few email-related things, primarily @chat.wordpress.org. I don’t think what I’m working on would be affected by anything here.

      • Jen 11:08 pm on November 18, 2014 Permalink | Log in to Reply

        cc @barry ^^

      • Ian Dunn 1:26 pm on November 19, 2014 Permalink | Log in to Reply

        If there isn’t a consensus for setting up real mailboxes, we could work around that for SupportFlow installs by setting up foo@wordpress.org aliases that forward to wordpress-foo@gmail.com, and then connect the Gmail account to SupportFlow.

        One drawback to that is that replies to the user would be sent from the Gmail account, rather than the WordPress.org account. That’s not a big deal, but it does feel a little janky, and the user will end up with two addresses in their address book for the same entity.

        • Dion Hulse 4:11 am on November 20, 2014 Permalink | Log in to Reply

          I don’t have any knowledge of how SupportFlow works, but is there any reason why the email would have to be sent via the mailbox?
          Couldn’t you just use the WordPress.org outgoing SMTP & BCC the email to the gmail account if required?

          • Ian Dunn 12:06 pm on November 20, 2014 Permalink | Log in to Reply

            Sorry, I’m not folllowing. Are you saying it’s possible to setup a foo@wordpress.org alias, and then send mail from it as if it were a regular account? Or that the current @wordpress.org addresses have regular SMTP accounts, but with the mailbox disabled?

            In my limited experience, the ability to send mail from an address is coupled with having a mailbox, but maybe that’s just an artificial restriction that things like Plesk have added on top of the mail service itself?

            • Samuel Wood (Otto) 11:32 pm on November 21, 2014 Permalink

              I’m not entirely certain on all the details, but no, an “account” is not necessarily linked to a sending address.

              For example, for the themes supportpress (where commercial theme listings are handled), there is a forward to a gmail account. SP retrieves the email from there. But any replies are actually sent back through our own SMTP server at mail.wordpress.org. So, the gmail account never actually sees the replies, we don’t send replies back through it or from it. It’s just a receiving box and holding area (and spam-scanner).

              I am unfamiliar with Plesk.

            • Ian Dunn 8:58 pm on November 23, 2014 Permalink

              Ah, ok. I think that would work for our purposes, then.

  • Jen 6:52 pm on May 26, 2013 Permalink |
    Tags: ftp,   

    @barry, @stankea, etc: Otto has the only ftp creds for wp10.wordpress.net, and others need to be able to change images in the theme folder etc. Can you create another ftp account for me, and David and George and I will just share it?

    Need this to send out wp10 uploading instructions to all the parties around the world (Australia etc 27th is today not tomorrow), so need access relatively urgently. Thanks, and sorry to interrupt your weekend.

  • Andrew Nacin 5:46 pm on May 10, 2013 Permalink |
    Tags: archive.wordpress.org, server   

    We need a new VM on xen1.lax for archive.wordpress.org, which should have nginx-base but not PHP. A new wporg-archive role should have the bare minimum – just an nginx config that listens on archive.wordpress.org (SSL not needed) and serves up static files in /home/archive/public_html.

    The SSH keys for coffee2code, otto42, and myself should be installed for the archive user. Ideally the user should have the ability do to the following:

    • sudo /usr/bin/vim /usr/local/etc/conf.d/archive.wordpress.org.conf
    • sudo /etc/init.d/nginx reload

    (This has been discussed with and signed off by @barry)

  • Jen 7:11 pm on April 9, 2013 Permalink |
    Tags: site setup, wordpress.net,   

    WP10 Site 

    Hi all. We need a wp install set up at wp10.wordpress.net for the 10th anniversary parties site. Matt would like it there rather than on .org, but @otto42 doesn’t have access there. Can someone set it up and make me an admin? Thanks.

    • Andrew Nacin 7:37 pm on April 9, 2013 Permalink | Log in to Reply

      wordpress.net is where things go to rot, nor is it taken seriously. wp10.wordpress.org makes far more sense. If there’s a concern that it’s an extra subdomain to maintain, I don’t find that to be a problem — it’s one line in an existing nginx file, followed by a new site on the network. Much easier than something new on multipattern. Also, wp10 is unique, it isn’t going to clash with a language or something else in the future. Ten years is a big deal, we shouldn’t hide it on .net.

      FWIW, wikipedia.org did http://ten.wikipedia.org in 2011 and they surely intend to keep that archive around.

      • Jen Mylo 7:40 pm on April 9, 2013 Permalink | Log in to Reply

        If the URL is under discussion, another option I didn’t think of when talking to Matt earlier would be to put it up at meet.wordpress.org/wp10 (or /ten or /10) if we got moving on getting the meet section up there with the feeds from meetup.com. Kind of would make sense?

    • Barry 11:17 pm on April 10, 2013 Permalink | Log in to Reply

      Happy to do whatever, we just need to know what URL to use.

    • Barry 1:57 pm on April 17, 2013 Permalink | Log in to Reply

      Any updates here?

  • Jen 6:33 pm on December 11, 2012 Permalink |

    Hey @barry and @stankea. Can you set up an email address (not a box, just an alias) of meetups@wordpress.org and have it forward to me at jane@automattic.com? At some point we’ll probably want to set up a supportpress instance or something, but for now I just need an active address to satisfy the meetup.com contract. Thanks.

  • Andrew Nacin 2:06 pm on October 28, 2012 Permalink |
    Tags: wpcs   

    Community Summit Task/Project List 

    Rearranging Directories




    Other Projects

    Other things @barry expressed interest in (low priority) —

  • Samuel Wood (Otto) 9:26 pm on July 17, 2012 Permalink |  

    Problem with nginx rewrites, I think. Conflict between the new make.wp.org/support and the support forums.


    Incorrectly redirects to:


    The make site is currently set to default permalinks to work around this for now. Can the nginx rules be modified to handle this case?

    • Andrew Nacin 10:20 pm on July 17, 2012 Permalink | Log in to Reply

      Inside the $host = make.wordpress.org conditional, it should end with rewrite ^. /index.php last;, which is what ends the @404-extend block. This will prevent rewrites designed for ^wordpress.org from causing problems elsewhere.

      learn.*, make.* and future subdomains should probably end up in their own stripped down wporg-wp.wordpress.org config file, as the relevant subdomains here run a mostly stock WP network, but I’ll leave that to @barry and @stankea.

      • Barry 10:30 pm on July 17, 2012 Permalink | Log in to Reply

        Thanks – fixed.

        @stankea – can you please look into breaking these things like make and learn into their own server blocks to make things less complicated? Thanks.

  • Matt Mullenweg 7:24 pm on July 17, 2012 Permalink |
    Tags: network,   

    Daniel Convissor is having trouble reaching plugins.svn.wordpress.org, here’s a traceroute:


    Is this a broader issue?

    Will give his email to @barry on Skype if any more info is needed.

    • Barry 8:04 pm on July 17, 2012 Permalink | Log in to Reply

      I emailed Daniel. There are some UDP filters upstream which is why the traceroute doesn’t work. This should not affect HTTP/HTTPS traffic. I asked him for more details about what exactly he is having trouble with.

compose new post
next post/next comment
previous post/previous comment
show/hide comments
go to top
go to login
show/hide help
shift + esc