Opened 9 years ago

Closed 6 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:

Description


Subtickets

Change History (5)

comment:1 Changed 9 years ago by Sam Kleinman

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 Changed 9 years ago by Christopher Allan Webber

You're welcome to accept this one!

comment:3 Changed 9 years ago by Christopher Allan Webber

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

comment:4 Changed 8 years ago by Christopher Allan Webber

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.

Thanks!

comment:5 Changed 6 years ago by Ben Sturmfels

Owner: Sam Kleinman deleted
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.