Lighting Thoughts on Lighting Deploy

and in due to the fact that the

this you have in the fact that back

to you in a friends my name is

Christina Simon Engineering Dir. economy house which is basically a publication company in New York City and I'm really excited talk about imbecilic play in particular the lighting deployment schedule as all the background icon

daily-use ever to power homegrown internal seen as called co-pilot and actually this and replicated then in production for 5 years it's going pretty strong It's a multi-tenant applications so what that means is that editors from all of our different brands comes 1 single somone co-pilot to create and publisher content to the Web another exciting news sometime last year we decided to expand your sister international overseas economies many the lot extensions scale there was a really good opportunity for us to think about how take another look at a deployment workloads you can streamline that the current deployment

workflow that's a bit like this say you're a brand new 1 added fuel to your form templates vote to offer you actually have to bring down the co-pilot repository make committed that we which inches of build on a continuous integration server Jenkins we and that is 1 has and never build traits of that that's in copies over the server to be deployed everyone then to promote this seems to staging and production we have to have the goes that workflow again this is not completely ideal for us it's not ideal is really time-consuming at least for replication that Jenkins built to take 20 minutes to do PMI and so on rebelled into on a test suite so from the local development to production you're looking at like at least 1 hour without you at and that's really inopportune you're trying to get a hot fix not really quickly additionally there were no isolation changes so that 1 change to vote template had to be a point the entire multi-tenant applications we think we can do better the team side to look into embassy owing to play which is basically an ion for and bring a single interface for deploying and applications in particular we looked at the embassy elided deplete point like impact which is 1 of plug-ins what is the Bislett talk about and actually that were really need to use this infrastructure backpack also employs employs the

lightning deployment strategy which I think is the revealing a refresher role you have about 3 steps 1 the builder a replication bozos assets to the place those efforts to due 2 different targets and NS 3 and the other 1 actually caches units additional block to add is key by the version know when you're gonna red even after the pathogen by just putting the current pointer to the version that you want in this example to 1 beat so we like like shows you what we wanted so much we decided

to break out 1 with application to multiple modules and then break that members light apply and each 1 of those models then so in this diagram in the middle you have a common functionality of a CMS and then each bring this zone model and every time you 1 embassy elided play it produces a lot of great building blocks that we can use to mix and match and create a file organizational mobile to be deployed out to our customers

concretely and those building blocks are the red is entries for what is currently accurate in court and what is currently activity for the brand concerned with in this case vote initially the is the annotation all file Skelton that we can use the previous 2 entries to kind of inject the script tags for what we need to produce a final index file over on the right so now the current appointment looks live it like this

developer can make the Committee just their brand bundle which kicks off an imbecile I'd applied in combination with the poor and appointment artifacts we can create a final innovation on how to be serviced by observers and that even better part is that just to promote that change seating production you just have to update some pointers so those a lot

hand-waving by and other the day and is that assail I'd play gave us a lattice have instantaneous releases with all we had to do with update Redus entries we have independent isolated deployments program because we had these separate models and node apologize energy would be good without the downtime

and so for more documentation and examples you can look at Embassy like what our common has a really really great information and again many interesting and thank benefactor

dependent due to the fact

this fact then in fact what happened

the the new I would that

be the and in fact what

happened