Closed Bug 696378 Opened 13 years ago Closed 13 years ago

Manual deploy of drumbeat required

Categories

(Infrastructure & Operations Graveyard :: WebOps: Labs, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: boozeniges, Unassigned)

Details

We're looking to push out a change to our branding on Drumbeat.org and with no Paul we've got a bit of a problem doing so.

Current code can be found https://github.com/paulosman/batucada, and it already seems to be up and running on https://batucada.mozillalabs.com/en-US/

Any problems please let me know
(In reply to Ross Bruniges from comment #0)
> We're looking to push out a change to our branding on Drumbeat.org and with
> no Paul we've got a bit of a problem doing so.
> 
> Current code can be found https://github.com/paulosman/batucada, and it
> already seems to be up and running on https://batucada.mozillalabs.com/en-US/

So you need latest code from https://github.com/paulosman/batucada to be pushed live to drumbeat.org, correct ?

Can I do this anytime ?

In the future, access to this VM should be granted to someone else on the drumbeat project.
Status: NEW → ASSIGNED
Heya Gozer, 

Yeah, that's exactly right :) I can see that it's already up and running on staging (https://batucada.mozillalabs.com/en-US/)

Will open a bug to get myself access but what would also be very cool would be if you could give me a walk-through of the steps you need to take to get the code live. I'm not really a server type person but I'm sure if I was shown what was needed I would get my head around it nice and easily. Am happy to be around at a a time that suits you.

Thanks very much, any further probs please let me know, 

Ross
Zandr and I sorted out a basic way to do this yesterday during the festival, this should tide us over for now.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.