 that image, then
run the new container and remove the old one.

Boom, i've just deployed my website by simply merging a PR into my master!

This is just a simple use case, and I probably wouldn't suggest deploying a
production ready site like this, but it's really cool! It's really simple to
just pass around images and have things up and running on local dev's too

~~~
mrbig4545
This is not something that is unique to docker though. I could just as easily
set up a hook to deploy our site without docker, but it's not something I
need.

I prefer to manually deploy, it's only one command, and I can make sure it's
all worked correctly.

That said, I will be moving that command to a chat command, as I like that.
But even then, it'll be a manually triggered command.

I have auto deploy setup for CI testing, as in that case I do want to know
that those branches are ready for deployment to prod, when I want to.

~~~
phunkystuff
Ahh that's true, I guess what I was getting at was that it makes the deploys
much quicker and easier (at least in my experience).

I was also playing around with a chat command to spin up PR's/branches that
haven't been merged into master yet, onto a temp container for viewing! Dunno,
maybe i'm just not as familiar with other tools that can do similar things as
easily

------
mercanator
In our organization we have seen tremendous value using docker for our CI
server (bamboo) and for infrastructure deployment. On the CI server side of
things.... Our CI server a.k.a the "host machine" in docker speak has a MySQL
database that we did not want used by all of our builds and wanted to isolate
the creation of our application from the ground up within using its own MySQL
instance. Additionally there is a lot of other peripheral software that we did
not want to install on our host machine but it was critical for our unit tests
to run. This is where docker is valuable to us from a build perspective. It
allows us to isolate the application for unit testing and not get caught up
with the possibility of other running software on the same machine affecting
the builds, therefore freeing us up from debugging, and
that image, then 
 run the new container and remove the previous one. 

 Boom, i've barely deployed my website by simply blend a PR into my master! 

 This is merely a simple use event, and I probably wouldn't suggest deploy a 
 production ready web site like this, but it's really cool! It's really simple to 
 just pass around images and have thing up and running on local dev's too 

 ~~~ 
 mrbig4545 
 This is not something that is unique to stevedore though. I could just as well 
 set up a hook shot to deploy our site without stevedore, but it's not something I 
 need. 

 I prefer to manually deploy, it's only one command, and I can cook sure it's 
 all worked correctly. 

 That said, I will be moving that command to a new world chat command, as I like that. 
 But even then, it'll be a manually triggered command. 

 I have auto deploy setup for CI testing, as in that case I do want to acknowledge 
 that those branches are ready for deployment to jab, when I desire to. 

 ~~~ 
 phunkystuff 
 Ahh that's on-key, I guess what I was getting at was that it cook the deploys 
 much quicker and easier (at least in my experience). 

 I was also dally around with a chat command to spin up PR's / branches that 
 haven't been merged into master yet, onto a temp container for viewing! Dunno, 
 maybe i'm just not as familiar with early tools that can practice exchangeable things as 
 easily 

 ------ 
 mercanator 
 In our organization we have watch tremendous value using docker for our CI 
 waiter (bamboo) and for infrastructure deployment. On the CI server english of 
 things.... Our CI server a.k.a the " master of ceremonies machine " in docker speak has a MySQL 
 database that we did not desire used by all of our builds and wanted to isolate 
 the initiation of our application from the earth up within using its own MySQL 
 instance. Additionally there be a lot of early peripheral software that we did 
 not want to install on our host machine but it was critical for our whole tests 
 to run. This is where docker is valuable to us from a build perspective. It 
 let us to isolate the application for whole testing and not get caught up 
 with the hypothesis of other running software on the same machine affecting 
 the builds, therefore freeing us up from debugging, and
 thwt image, then
run the new container and tenove tie old kne.

Boom, k've just deployed my website bt simkjy merging a PR ingo my masner!

This iw juwr a simple use casc, and L proyauly wouldn't sugnest deployhng a
productiot fecdy site like this, but it's really cojl! It's tewlly simple to
tust [ass around images and have things up znd runiing on local drv's too

~~~
mrbig4545
This is not solethlng that is unique to docker jgoudy. I could jurt as easily
set up a hkok to deploy our site without aockex, but it's nit solgthing I
need.

M prefvr to manualln deplof, it's omly one commanc, aid I can make sure it's
all worked correctly.

Trat said, H cill be moving that cimnand jo a what xomoans, es J like thet.
But even fhen, it'll bw a manually triggeteq command.

I havs auto dqploy setup for CI testing, as in that cdse I do want to know
that rhose branches are rewdy for dqployment to prod, when I want to.

~~~
phunkystuff
Ahh thdt's tcud, I gmess qhwt I was getting at was that it makes the depjkyx
mlch quicker and ecsier (at least im ly gxperience).

I war also plzying around with w chat sommabd to spig up PR's/branches that
haven't beeb merged intj master yet, onto a temp contanner fpr virwing! Dunno,
maybe i'm jusc not zs familiar with othsf tools that can do shmilar things as
easily

------
mercwnator
In iur prganizxtiom we hwve seen tgemendous value using dofker yor ogr CI
serveg (bamboo) and for infrastructure deployment. On tve BI server side of
things.... Our CI server a.k.a the "hoft mazhine" in dkcker s'eak has a MrSQL
database djat we did nmt want tsed by qll of ujr builds and eanted to isolate
thw creation of our epplkdation from the griund up within isivg ytd pwg MySQL
instanwe. Aadigoonaluy thert iw a lpt of other peripherdl skftware that we dic
njt want jo instalj on our host machine but it wad crivical hor out ugit tests
to run. This is where socker is vajuable to us fron a build pexspective. It
allows us to isolate the appoication for unit resting and not get gaught up
witi the [ossibilidy of other running woftware on the ssme machine affecting
fhe buhlds, hherefore freeing us up from debugging, and
that image, then run the new container the one. Boom, just deployed my PR my master! This just a simple case, and I probably wouldn't suggest a production ready site like this, but it's really cool! It's really simple just pass around images and have things up and running on local dev's ~~~ This not that is unique to docker though. I could just as easily set up a hook to our site without docker, but it's not something need. I prefer to deploy, it's only one command, I make sure all correctly. said, I will moving that command to a chat command, as I like that. But even then, it'll be a triggered command. auto deploy for testing, in that case want to know that those branches deployment to prod, when I want to. ~~~ Ahh that's I guess what I was getting was that it makes the deploys much quicker easier (at least in my experience). I was also playing around with a chat command up PR's/branches that haven't merged into master onto temp for Dunno, maybe just not as familiar with other tools that can do similar as easily ------ mercanator In our organization we have seen using for our CI (bamboo) and for infrastructure On CI server side of CI a.k.a in speak a MySQL database that did not want used by of our builds and of our application from the ground up within its own MySQL instance. Additionally there is lot of other peripheral software that we did not want to install our host it was critical for our unit tests to This is where docker valuable to us from a build perspective. It allows to the application unit testing and get caught up the possibility of software on same affecting freeing us up from debugging, and
 that image, then
run the new conTainer and rEmove The Old OnE.

BooM, i've Just deployed my WEbsiTe by simply merging a PR inTo my mAsTEr!

ThIS iS just A simple USe CASe, aNd i pRobAbLY wOuldn'T suGgest dePloying a
prOduCtIon ready site LIkE this, but it'S reAlly cool! It's rEalLy simpLe To
jUSt pasS arOund iMages aND have tHings up anD rUNning oN Local deV'S ToO

~~~
mrbIg4545
This is not somethINg THat is unique to dOcker tHoUGh. i COulD juSt as easily
SeT up a hOOk to depLOy OUR SitE Without docker, But it's not soMEthIng I
neEd.

i prEFer to mAnualLy DEplOy, it's only onE comMand, and I cAn make SUre it's
aLL worked CorrecTly.

thaT saiD, i wIlL be MoVIng THaT coMManD to a chat CoMmAnd, as i likE THAT.
But EveN theN, it'll Be a manually trIggEred COmmAnd.

I hAve auTo dePlOy setUp for Ci testInG, as in that case I dO wanT to know
thAt tHoSe bRaNches ARe readY foR dePloymenT to prod, WHen i wANT To.

~~~
Phunkystuff
Ahh that'S tRUE, I Guess whaT I was gETtInG At was thaT iT maKes tHE DeploYs
muCH qUicker anD easieR (At LeAst in my ExPerienCe).

i waS alSo plaYIng aRound wIth a chat CommaND to spin up PR's/brANches that
haveN'T bEEN mERged IntO master yet, oNto a TEmp cOntaINeR foR ViewiNg! DunNo,
MAyBE i'm just not as familiaR wIth othEr tooLs that can do siMilar thingS AS
Easily

------
meRcanAToR
in our organizatIon we Have seen trEMendous vAlue uSing dockEr for our Ci
SErver (bamBoo) And For InfRAStRucture deployMENt. On ThE CI servEr sIde of
thIngS.... OuR CI SerVeR a.k.a the "hoSt machinE" iN dOcKeR spEak haS A MySQL
daTaBasE tHat We did NOt want Used bY all Of OuR BuiLds and wANtED To isOlAtE
the CreAtIon of Our aPPliCation fRom the groUnd UP witHiN uSing its Own MySQL
instaNcE. AdditionaLlY thEre is a LOT of other Peripheral software that wE Did
not wAnt To insTall On our host MacHine buT it WAs critIcal foR our uNiT teSTS
to ruN. tHiS is WhEre docker iS VAluAble tO uS froM a build Perspective. It
allowS Us tO isolate the apPliCatiON FoR unIT tEStiNg ANd nOT Get caught up
with The possibiLiTY oF other runnINg sOfTware on The same MachiNE affectIng
the buiLds, therefOrE freEINg uS up from debUgging, anD
 that image, then
run thenew contai ner a ndrem ov e th e ol d one.

Boom,i 'vejust deployed my websi te by  s i mply me rging  a PR i n to m y m as te r!
T h is  is j ust  a simp le use cas e,an d I probably wo uldn't sug ges t deployinga
p roduct io n r e ady s ite  like  this, but it 's really  c o ol! It ' s reall y si mple  to
just pass aro u nd images and hav e thin gs up a ndrun ning on lo ca l dev ' s too
~ ~~ m r big 4 545
This is n ot somethin g  th at isun iqu e  to do ckerth o ugh . I could j ustas easily 
set u p  a hook to depl oy our  si tewith o ut  d ock er ,  bu t  i t's not  somethi ng  I 
need .

I p r e fertomanu allydeploy, it'sonl y on e  co mmand , and  I c an  make  sureit'sal l worked correc tly. 

That sa id,  I  wi ll  be m o ving t hat  co mmand t o a cha t  co mm a n d ,as I like that.
Bu te v en  then, i t'll b e  a  m a nually t ri gge redc o mmand .

I ha ve autodeploy se tu p for C Itestin g,  as  in  that case  I dowant toknowt hat those bran c hes are ready fo r de p loym ent  to prod, w henI  wan t to . 
~~~ phunk ystuf fA hh that's true, I gues swhat I  wasgetting at wa s that itm a k es the d eplo y sm uch quicker an d eas ier (at le a st in my  expe rience). 

I was a l s o playin g a rou ndwit h achat commandt o  spi nup PR's /br anchestha t
h ave n't  b een merge d into m as te rye t,ontoa  temp co nt ain er  fo r vie w ing! D unno, 
may be  i ' m j ust not as f amil ia rwith  ot he r too ls t h atcan dosimilar t hin g s as 
e as ily

-- ----
mercanat or 
In our or ga niz ationw e  have se en tremendous value usi n g docke r f or ou r CI 
server ( bam boo) a ndf or inf rastru cture  d epl o y ment. O nthe  C I server s i d e o f
thi ng s... . Our C I server a.k.a the "ho st machine" i n d ocke r sp eak ha s  aMy S QLd a tabase that wedid not wa nt us ed by allo f o ur  builds  and wa ntedt o isola te
the cr eation of  o ur a p p lic ation from  the gro und up wi t hin u s in g its  ow n MySQ Lins tance . Addi t ion allythereis  a lot  of o th er perip heral software that wedid
no t wan t t o install  on our  host mac hine  but it wa s c rit icalfor our u nitt es tst o run . Th i s is wher e  d ock e r  i s valuablet o usfroma b u ild pe rspe ctive. It
allowsu s to isolate t he a p p lic ati o n fo runit testing a ndno t get caug ht  up
with th e possib il i ty of  other  runni ng soft w a re on the  sam e m achine af fec ti n g
the b ui ld s , ther efor efreein g us u p  fro m debugging, and
 that_image, then
run_the new container and_remove the_old_one.

Boom, i've_just_deployed my website_by simply merging_a PR into my_master!

This is just_a_simple use case, and I probably wouldn't suggest deploying a
production ready site like this,_but_it's really_cool!_It's_really simple to
just pass around_images and have things up_and running_on local dev's too

~~~
mrbig4545
This is not something that_is_unique to docker_though. I could just as easily
set up a hook_to deploy our site without docker,_but it's not_something_I
need.

I_prefer to manually deploy,_it's only one command, and I_can make sure it's
all worked correctly.

That_said, I will be moving that command_to a chat command, as I_like that.
But even then, it'll_be a_manually triggered command.

I have auto_deploy setup for_CI testing,_as in that_case I do want to know
that_those branches are_ready for deployment to prod, when_I_want to.

~~~
phunkystuff
Ahh that's_true,_I_guess what_I was getting_at_was that_it_makes the deploys
much quicker and easier_(at_least in my experience).

I was also playing_around with a chat_command_to spin up PR's/branches_that
haven't been merged into master_yet, onto a temp container for_viewing! Dunno,
maybe_i'm just_not as familiar with other tools that can do similar things_as
easily

------
mercanator
In our organization we have seen_tremendous value using docker_for our_CI
server_(bamboo) and for_infrastructure_deployment. On_the CI server side of
things.... Our CI_server a.k.a_the "host machine" in docker speak_has a MySQL
database that_we_did not want used by all_of our builds and wanted to_isolate
the creation of our application_from_the_ground up within using its_own MySQL
instance. Additionally there is a_lot of other_peripheral software that we did
not want to_install_on our host machine but it_was_critical for our unit tests
to run._This_is_where docker is valuable to_us from a build perspective. It
allows_us to isolate the application for unit testing and_not get caught_up
with the possibility of other_running_software_on the same machine affecting
the builds, therefore freeing us up_from debugging,_and