Repo & Deployment access

[ralphbean]

In preparation for the porting fad this weekend, can we open up the group of people who can update the app some? This way, everyone can be a little more coordinated in their tasks and they can show off the fruits of their labor more quickly.. with less friction. We'll need people who can:

• push to github
• push to openshift

Can I request that myself and @abadger be added to the github group? For openshift, my openshift account is associated with ralph.bean@gmail.com and @abadger is associated with a.badger@gmail.com.

[sYnfo]

@ralphbean I believe the app is set to automatically redeploy on new commits (though @encukou will know for sure).

I've sent you and @abadger an invite to the fedora-python group. [EDIT: never mind, I've added you as collaborators to this repo]

[encukou]

A push to Openshift will trigger a redeploy, but it does take a minute to update the DB, so I worry that simultaneous pushes might not be good for the system. (worry == I don't want to start trying it at the FAD)
I'm happy to hand out access if you send me your SSH keys, but we should coordinate so that there's only one person pushing at a time. How do hand-overs either here or on IRC sound?

[ralphbean]

Yeah, let's just rely on the auto re-deploy behavior. That seems easiest. Will see you in IRC tomorrow. Thanks!

[ralphbean]

Odd, I pushed cce047b but the app didn't seem to update. (It worked locally when I tried serving the app).

[encukou]

I see I could have worded that better, sorry.
A {push to OpenShift} will trigger a redeploy. Not a push to GitHub.

[ralphbean]

Ah, I see. Could you add ssh keys for myself and @abadger?

• @ralphbean is here
• @abadger is here

[encukou]

Added.
Sorry for not responding earlier, I was at PyCon CZ and lost this comment in the storm of pull request e-mails :(

[encukou]

Aaaand the remote is ssh://560d3fd12d5271847c000146@portingdb-encukou.rhcloud.com/~/git/portingdb.git/

[ralphbean]

Thanks @encukou!