Opened 12 years ago

Closed 10 years ago

#424 closed task (invalid)

Create Fabric Deployment Script for Media Goblin

Reported by: Sam Kleinman Owned by:
Priority: minor Milestone:
Component: documentation Keywords:
Cc: Parent Tickets:


Change History (5)

comment:1 by Sam Kleinman, 12 years ago

I'll help, perhaps even accept assignment for this ticket, but if someone else is eager to work on this, I don't want to get in anyone's way.

comment:2 by Christopher Allan Webber, 12 years ago

You're welcome to accept this one!

comment:3 by Christopher Allan Webber, 12 years ago

Component: component1documentation
Owner: changed from somebody to Sam Kleinman
Status: newassigned

comment:4 by Christopher Allan Webber, 11 years ago

Status: assignedin_progress

Hi! I'm moving this ticket from "assigned" to in_progress per our new workflow. Please update the ticket and let us know if you're still working on this. If you are, super great! If not, we'll remove the claim and move it back to "accepted" in a couple of weeks.


comment:5 by Ben Sturmfels, 10 years ago

Owner: Sam Kleinman removed
Resolution: invalid
Status: in_progressclosed

Unless you're deploying to some sort of abstract "platform as a service" like OpenShift, hosting environments, and indeed different PaaS providers, vary too much to write a one-size-fits-all Fabric script.

Where Fabric really shines is when you have to regularly perform a complex process to deploy updates to a custom web app in custom hosting environment. When you have to perform updates multiple times a day, this type of automation saves a lot of time and mistakes. This isn't really the same use case as for MediaGoblin though, where it will normally be deployed once and then used without updates for perhaps months or more.

Please feel free to reopen this request if you have further thoughts on this.

Note: See TracTickets for help on using tickets.