 Dockercon on introducing Docker to Demonware
for CI across a variety of projects. I don't think the video is up yet, but
it's well worth a watch if you're thinking of bringing it into your company.
In the meantime we wrote a blog post on his talk:
[http://blog.codeship.com/dockercon-2015-using-docker-to-
driv...](http://blog.codeship.com/dockercon-2015-using-docker-to-drive-
cultural-change-in-gaming/).

~~~
bampolampy
We are just starting a beta for our new CI flow which follows the container
paradigm very closely. It allows you to build docker compose stacks for your
various application images, and run your CI/CD pipeline locally, exactly as it
would get run on our hosted platform.

If anyone is interested in joining our beta, just drop me an email: brendan at
codeship.com.

------
yebyen
I honestly don't know how much those things cost (I have heard some people say
AWS is not cheap, but compared to buying your own hardware maybe all of this
stuff is very cheap). The point of asking is, my company has not found a clear
place to use Docker directly, but we do use it indirectly through the Deis
project, and CoreOS.

My experience with Deis has been wonderful. If you ever looked at Heroku but
got to the pricing page and didn't look any further, Deis has the same
workflow (and much of the same stack, Cedar) as Heroku. The whole thing is
built on docker containers, and designed with failover in mind.

I see that Codeship costs a fair amount of money on the higher end of usage;
for the cost of a few months on their enterprise subscription, you could
probably build your own CI cluster on Deis. CoreOS also targets AWS, and I
don't have any idea what your AWS environment looks like, but you could likely
build a Deis cluster on AWS just as easily as you could on your own hardware,
if not easier.

I try not to think of Docker as an end so much as a means. For me, it doesn't
even matter that it's using Docker under the hood, but if you have
containerized your
Dockercon on introducing Docker to Demonware 
 for CI across a variety of projects. I don't think the video recording is up so far, but 
 it's well worth a watch if you're thinking of bring it into your company. 
 In the meantime we write a blog post on his lecture: 
 [ http://blog.codeship.com/dockercon-2015-using-docker-to- 
 driv... ](http://blog.codeship.com / dockercon-2015 - using - stevedore - to - drive- 
 cultural - change - in - gaming/). 

 ~~~ 
 bampolampy 
 We are just begin a beta for our new CI flow which follows the container 
 prototype very closely. It allows you to build docker compose stacks for your 
 assorted application images, and run your CI / compact disk pipeline locally, exactly as it 
 would get run on our hosted chopine. 

 If anyone is interested in join our beta, just drop me an email: brendan at 
 codeship.com. 

 ------ 
 yebyen 
 I honestly don't acknowledge how much those things cost (I have heard some people say 
 AWS is not cheap, but compared to buying your own hardware maybe all of this 
 stuff is very cheap). The point of asking is, my company has not found a clear 
 place to use Docker immediately, but we do practice it indirectly through the Deis 
 project, and CoreOS. 

 My experience with Deis has been wonderful. If you ever look at Heroku but 
 got to the pricing page and didn't look any further, Deis have the same 
 workflow (and much of the same stack, Cedar) as Heroku. The solid thing is 
 built on docker containers, and designed with failover in mind. 

 I visualize that Codeship costs a fair amount of money on the higher end of usage; 
 for the monetary value of a few months on their enterprise subscription, you could 
 probably build your own CI cluster on Deis. CoreOS also target AWS, and I 
 don't have any idea what your AWS environment looks like, but you could likely 
 build a Deis cluster on AWS just as easily as you could on your own hardware, 
 if not easy. 

 I try not to intend of Docker as an end so a lot as a means. For me, it doesn't 
 even matter that it's using Docker under the hood, but if you have 
 containerized your
 Dofkercon on introducing Ducker to Demonwcee
for RI acroas a varkety of projects. I don't thinn rhe vudeo is up yet, but
it's dell wortj a watcy if tou're thinking of nxingihn it nnvo your company.
Ln the meandime we wrote d cllg post on his talk:
[http://blog.codeship.som/dockrrfon-2015-using-docker-jo-
drin...](hetp://bmog.codeship.com/dockercon-2015-using-docker-fo-drive-
bultural-change-in-gsming/).

~~~
bampolampy
We are just stagting a beta for okr new CI foow ryich follows the contapuer
paradigm very closely. It allows you to cuild docker conpise vtacks for bour
vagious applicabpon imaces, and run your CI/CD pi'elibe locally, exactly as it
would get run og our hosdeb platform.

If anyone iw untergsted in giinkng onr geta, jkst drop me ah email: brebdan at
codeship.com.

------
ytbyqb
I honestly dkn't knjw how much those things cost (I have hearg skme people say
AWS is nor cheap, but compared jo buying rour own hardware maybe all of this
stuff is very wheap). Ghe pjkbt of asking is, my company has not found a cleaw
llscv to use Docker dlrectly, but we do isf oj indirectly tfrough ths Deis
project, and ForeOS.

Mi expeeience wiuh Deos has been wonderful. If yoy ever lookeb ar Heroku but
got to the priciny page and cidn't look any further, Beis hzs the same
aorkflow (zvd much of the sxme sdack, Cedar) as Heroku. The wrole thinj is
bbilt on aockgr contwiners, and desinted with failover ln miud.

I sae that Cofeship costs a fair amount of money on the hibhar vnd of uscge;
for the cost of w few months ou their znterpfise subscgiption, ymu could
profably build ymor own CI cluvter on Qeis. CorwOS alsu targets AWS, amd I
don't kcve any ieea what your AWS cnviruhment looks likz, vut you could lokeuy
btipd a Geis cluster on XWS kust xs easily aw you could on your own hdrdwzre,
if not easier.

I yrn not to jhink of Qocker as an rnd so much as a mtans. Fmr oe, it dogsn't
even matter that it's using Socker unfer the hood, bue if you have
concainerized your
Dockercon on introducing Docker to Demonware for a of projects. don't think the it's worth a watch you're thinking of it into your company. In the we wrote a blog post on his talk: [http://blog.codeship.com/dockercon-2015-using-docker-to- driv...](http://blog.codeship.com/dockercon-2015-using-docker-to-drive- cultural-change-in-gaming/). ~~~ bampolampy are just starting a beta for our new CI flow which follows the paradigm closely. allows to build docker compose stacks for your various application images, and run your CI/CD pipeline locally, as it would get run on our hosted If anyone is interested joining our beta, just drop an brendan at ------ I don't know how those things cost (I have heard some people say AWS is not cheap, but compared to buying own hardware of this is cheap). point of asking company has not found a clear Docker directly, but we do use it indirectly the Deis and CoreOS. My experience with Deis been wonderful. If you ever looked at Heroku got to the pricing page and didn't look any further, Deis has the same workflow of the same stack, as Heroku. The thing built docker and designed failover in mind. I see that Codeship costs a fair amount money on the higher end of usage; for the cost few on their enterprise you could probably build own cluster on Deis. CoreOS AWS, I idea your environment looks like, but could likely build a Deis on AWS just as your own hardware, if not easier. I try to think of Docker as an end much as a means. For me, it doesn't even matter that it's Docker under but if you have containerized your
 Dockercon on introducing DocKer to DemonWare
fOr Ci acRoSs a vArieTy of projects. I dON't thInk the video is up yet, but
iT's welL wORth a WAtCh if yOu're thiNKiNG Of bRiNgIng It INtO your ComPany.
In tHe meantime We wRoTe a blog post oN HiS talk:
[http://bLog.Codeship.com/dOckErcon-2015-uSiNg-dOCker-tO-
drIv...](httP://blog.cODeship.Com/dockerCoN-2015-Using-dOCker-to-dRIVe-
CultUral-change-in-gaminG/).

~~~
BaMPolampy
We are juSt starTiNG a BETa fOr oUr new CI floW wHich fOLlows thE CoNTAIneR
Paradigm very cLosely. It allOWs yOu to buIlD doCKer comPose sTaCKs fOr your
varioUs apPlication Images, ANd run yoUR CI/CD piPeline LocAllY, exaCTlY aS it
WoULd gET rUn oN Our Hosted plAtFoRm.

If aNyonE IS INterEstEd in JoiniNg our beta, just DroP me aN EmaIl: breNdan aT
codEsHip.coM.

------
yebyeN
I honEsTly don't know how mUch tHose thingS coSt (i haVe Heard SOme peoPle Say
aWS is noT cheap, bUT coMpARED tO buying your own hardWaRE MaYbe all of This
stUFf Is VEry cheap). thE poInt oF ASking Is, my COmPany has nOt founD A cLeAr
place To Use DocKeR diRecTly, buT We do Use it iNdirectlY throUGh the Deis
projeCT, and CoreOS.

My eXPeRIEnCE witH DeIs has been woNderFUl. If You eVEr LooKEd at HEroku BuT
GoT To the pricing page and DiDn't looK any fUrther, Deis has The same
worKFLOw (and mucH of tHE sAMe stack, Cedar) as herokU. The whole tHIng is
buiLt on dOcker conTainers, anD DEsigned wIth FaiLovEr iN MInD.

I see that CodeSHIp coStS a fair aMouNt of monEy oN thE hiGheR eNd of usage;
For the coSt Of A fEw MonThs on THeir enteRpRisE sUbsCriptIOn, you cOuld
pRobaBlY bUIld Your own ci cLUSter On deIs. CoReOs aLso taRgetS aWS, And I
don'T have any iDea WHat yOuR AwS envirOnment looks liKe, But you coulD lIkeLy
builD A deis clusTer on AWS just as easily as yOU could oN yoUr own HardWare,
if not EasIer.

I trY noT To thinK of DocKer as An End SO Much aS A MeAns. foR me, it doesn'T
EVen MatteR tHat iT's using docker under the hood, BUt iF you have
contaIneRizeD YOuR
 Dockercon on introducingDocker toDemon war e
f or  CIacro ss a variety o f  pro jects. I don't think t he vi de o  isu pyet,but
it' s  w e l l w or th  awa t ch  if y ou' re thin king of br ing in g it into yo u rcompany.
I n t he meantimewewroteablo g  post  on  histalk:[ http:/ /blog.cod es h ip.com / dockerc o n -2 015- using-docker-to-d ri v ...](http://bl og.cod es h ip . c om/ doc kercon-201 5- using - docker- t o- d r i ve- cultural-chan ge-in-gamin g /). 

~~~ba mpo l ampy
W e are  j u ststarting abeta  for ournew CI flow wh i ch foll ows th e c ont aine r 
p ar adi gm ver y  c los e ly.  It allo ws  y ou to  bui l d d ocke r c ompo se st acks for your 
va riou s  ap plica tionimag es , and  run y our C I/ CD pipeline loc ally , exactly  as  i t
w ou ld ge t  run o n o urhostedplatfor m .
If a n yo ne is interested i nj o in ing ourbeta,j us td rop me a nema il:b r endan  atc od eship.co m.

-- - -- -yebyenIhonest ly  do n't  know howmuch t hose thi ngs c o st (I have hea r d some people sa y AW S  isnot  cheap, but  com p ared  tob uy ing yourown h ar d wa r e maybe all of this 
s tuff i s ver y cheap). The  point ofa s k ing is,my c o mp a ny has not fou nd aclear
plac e  to useDocke r direct ly, but w e do use i t i ndi rec tly t hr ough the Deis p roje ct , and C ore OS.

My  ex per ien cewi th Deis h as beenwo nd er fu l.If yo u  ever lo ok edat  He rokub ut
got  to t he p ri ci n g p age and di d n 't l oo kanyfur th er, D eish asthe sam e
workflo w ( a nd m uc hof thesame stack, C ed ar) as Her ok u.The wh o l e thingis
built on docker cont a iners,and  desi gned  with fai lov er inmin d .

I s ee tha t Cod es hip c ostsa fa iram ount of mo n e y o n the  h ighe r end o f usage;
for the c o stof a few mont hson t h e ir  en t er p ris es ubs c r iption, you cou ld
probabl yb ui ld your ow n  CI  c lusteron Deis . Cor e OS also  targetsAWS, andIdon' t hav e any idea  what yo ur AWS en v ironm e nt  look s l ike, b ut  yo u cou ld lik e lybuild  a Dei scluste r onAW S just a s easily as you could o n your  ownhar dware,
if  no t  ea sier.

Itrynot to thi nkofDocke r a s  an e nd s o  m uch as amean s . For me, it  do e s n' t
even matt e r tha t it' s u s ing Do cker  under the hood,b ut if you have 
con t a ine riz e d yo ur 
 Dockercon_on introducing_Docker to Demonware
for CI_across a_variety_of projects._I_don't think the_video is up_yet, but
it's well worth_a watch if_you're_thinking of bringing it into your company.
In the meantime we wrote a blog post_on_his talk:
[http://blog.codeship.com/dockercon-2015-using-docker-to-
driv...](http://blog.codeship.com/dockercon-2015-using-docker-to-drive-
cultural-change-in-gaming/).

~~~
bampolampy
We_are_just_starting a beta for our_new CI flow which follows_the container
paradigm_very closely. It allows you to build docker_compose_stacks for your
various_application images, and run your CI/CD pipeline locally, exactly_as it
would get run on our_hosted platform.

If anyone_is_interested_in joining our beta,_just drop me an email: brendan_at
codeship.com.

------
yebyen
I honestly don't know how much_those things cost (I have heard some_people say
AWS is not cheap, but_compared to buying your own_hardware maybe_all of this
stuff is very_cheap). The point_of asking_is, my company_has not found a clear
place to_use Docker directly,_but we do use it indirectly_through_the Deis
project, and_CoreOS.

My_experience_with Deis_has been wonderful._If_you ever_looked_at Heroku but
got to the pricing_page_and didn't look any further, Deis has_the same
workflow (and much_of_the same stack, Cedar)_as Heroku. The whole thing_is
built on docker containers, and designed_with failover_in mind.

I_see that Codeship costs a fair amount of money on the_higher end of usage;
for the cost_of a few months_on their_enterprise_subscription, you could
probably_build_your own_CI cluster on Deis. CoreOS also targets_AWS, and_I
don't have any idea what your_AWS environment looks like,_but_you could likely
build a Deis cluster_on AWS just as easily as_you could on your own_hardware,
if_not_easier.

I try not to think_of Docker as an end so_much as a_means. For me, it doesn't
even matter that_it's_using Docker under the hood, but_if_you have
containerized your