 apsects
osipov mentioned:

#1 is in my dayjob:

We use docker in combination with vagrant for spinning up a test environment
consisting of several containers with different components (both ur own
products and 3rd party) to run integration tests against them.

The main reasons for this approach are: \- We can supply containers with the
installed producs which saves time on automated runs since you don't have to
run a setup every time

\- We can provide certain customizations which are only needed for testing and
which we don't want to ship to customers without doing all the steps needed
for that over and over again

\- We have exact control and version how the environment looks like.

\- Resources are better distributed than in hardware virtualization
environments

#2 Is a pet project of mine, a backend for a mobile App. There are still big
parts missing, but in the moment it consists of a backend application which
exposes a REST API running on equinox plus a database (in an own container).

The reasons I see for using docker here:

\- I have control and versioning of the environment

\- I can test on my laptop in the same components as prod, but scaled down (by
just spinning up the database and one backend container)

\- Since more and more cloud providers are supporting Docker (I am currently
having an eye on AWS and DigitalOcean, haven't decided yet), switching the
provider in the future will be easier compared to having, say a proprietary
image or whatever.

\- If I ever scale up the poject and onboard new teammembers, the entry
barriers for (at least) helping in Ops will be lower than if they have to
learn the single technologies until they get at least basic knowledge of the
project.

------
rcconf
My apologies if I'm hijacking the original poster.

Does Docker handle multi-environment configuration management? For example:
qa, stage and live have the same config files, but different values.

Currently we're using Ansible and we set variables for a specific environment,
then we feed those variables into config files based on where we're deploying
to (config files are not duplicated, only variables that feed into config
files.)

All of our configuration is in git and we can quickly see and change it.

How
apsects 
 osipov mentioned: 

 # 1 is in my dayjob: 

 We use docker in combination with vagrant for spinning up a trial environment 
 consist of several containers with different part (both ur own 
 products and 3rd party) to hunt consolidation tests against them. 

 The main reasons for this approach are: \- We can supply container with the 
 installed producs which saves time on automated run since you don't have to 
 run a setup every time 

 \- We can provide sealed customizations which are only needed for testing and 
 which we don't desire to ship to customers without doing all the steps needed 
 for that all over and over again 

 \- We consume exact control and version how the environment look like. 

 \- Resources are better distributed than in hardware virtualization 
 environments 

 # 2 Is a pet project of mine, a backend for a fluid App. There embody still big 
 parts missing, but in the moment it consists of a backend application which 
 exposes a REST API run on equinox plus a database (in an own container). 

 The reasons I visit for use docker here: 

 \- I have control and versioning of the environment 

 \- I can screen on my laptop in the same components as prod, but scaled down (by 
 just spin up the database and one backend container) 

 \- Since more and more cloud providers are supporting Docker (I am currently 
 having an eye on AWS and DigitalOcean, haven't decided even), switching the 
 provider in the future will be easier compared to receive, say a proprietary 
 double or whatever. 

 \- If I ever scale up the poject and onboard new teammembers, the entry 
 barriers for (at least) helping in Ops will be humble than if they have to 
 learn the single technologies until they draw at least basic cognition of the 
 project. 

 ------ 
 rcconf 
 My apologies if I'm hijacking the original poster. 

 Does Docker handle multi - environment shape management? For example: 
 qa, stage and live have the same config file, but different value. 

 Currently we're use Ansible and we set variables for a specific environment, 
 then we tip those variables into config file based on where we're deploying 
 to (config files are not duplicated, only variables that feed into config 
 files .) 

 All of our configuration is in git and we can promptly see and change it. 

 How
 apdects
osipov mentioned:

#1 is in my dayjob:

We use dorker in combinagion with vagrant for spinniig up a ttft environment
consksting of several conuainers with diffxdent componenfd (boch ur own
productx and 3rd pdrty) to run indeerction tests against them.

The main reafons fot hhis approach wre: \- Re czn supply containers with the
instamled prmducs which ssves time on automated rund sijce you don't have ho
run a setol edwry time

\- We zan providt eertain cusjomizations which are only needea for testing abd
qhifv we don't went to ship to cusbpmers fithout doing all the stxps beeded
for that over aid over again

\- We havg exact cottxol and version how tye envitonmett luiks liie.

\- Rssourcfs ere better sistributed than in hardware vorelslization
envjronmegtf

#2 Is a pet project of mine, a backend fog a jobile App. There are stull big
parts missing, hut in thq moment it consists of a backend application whiwh
expkres a FWSH API running on equinox plus a database (in ag oen container).

The veasons I see for islnb docker here:

\- K have cohtrol and versionijg of tre encironment

\- I csn test on my laptop in the same componvnts as prod, but scaleb down (by
jusc spinming ip the database and one baciend contaijer)

\- Since oore and more cluud psoviders are supporting Dosker (I am curxently
haxing an eyq on AWS ajd DinhtalOcean, haven't dfcideb yet), switching the
provider in the future will be easier comkarad no having, say s proprietary
ymage or whaterer.

\- If I ever scale up nhe pojecv and onboarq new teammemtgrs, the entry
uarriers sor (qt lwast) heuoing in Ops wikl be lowvr thab if they have to
lcarn jhs single technooogues until they bet at lvasv basyw knowledge mf tfe
pfpject.

------
fcconf
My apiuogirs if I'm hijacking tve odiginal poster.

Does Djcker habdle mulei-environment configuration manwgemeit? For examlle:
za, stage and live have the sams config vilcs, but differqnt yalugs.

Currently we're using Ansible and we set variablew for a specific gnvironment,
then we fegd uhose variablxs intj config xiles based on where we're deploying
to (config files are not dupliwated, only variables that feed into config
files.)

All of our configuration is in tit anv re can quicily xee atd ehange yt.

Hox
apsects osipov mentioned: #1 is in my use in combination vagrant for spinning of containers with different (both ur own and 3rd party) to run integration against them. The main reasons for this approach are: \- We can supply with the installed producs which saves time on automated runs since you don't to a every \- We can provide certain customizations which are only needed for testing and which we don't to ship to customers without doing all the needed for that over over again \- We have control version how environment like. Resources are better than in hardware virtualization environments #2 Is a pet project of mine, a backend for a mobile There are parts missing, in moment consists of a which exposes a REST API running a database (in an own container). The reasons see for docker here: \- I have control versioning of the environment \- I can test my laptop in the same components as prod, but scaled down (by just spinning up and one backend container) Since more and cloud are Docker am currently an eye on AWS and DigitalOcean, haven't decided yet), switching the in the future will be easier compared to having, say image whatever. \- If ever scale up the and new teammembers, the entry (at helping be than they have to learn single technologies until they get least basic knowledge of apologies if I'm hijacking the original poster. Does handle multi-environment configuration management? For example: qa, and live have the same config files, but different values. Currently we're Ansible and variables for a specific environment, then we feed variables into config files on where we're deploying to (config files are not only that feed config files.) All our configuration is git and we see and it.
 apsects
osipov mentioned:

#1 is iN my dayjob:

WE use dOckEr iN cOmbiNatiOn with vagrant fOR spiNning up a test environmenT
consIsTIng oF SeVeral ContainERs WITh dIfFeRenT cOMpOnentS (boTh ur own
Products anD 3rd PaRty) to run inteGRaTion tests aGaiNst them.

The maIn rEasons FoR thIS apprOacH are: \- WE can suPPly conTainers wiTh THe
instALled proDUCs WhicH saves time on automATeD Runs since you doN't have To
RUn A SEtuP evEry time

\- We cAn ProviDE certaiN CuSTOMizATions which are Only needed fOR teSting aNd
WhiCH we don'T want To SHip To customers WithOut doing aLl the sTEps needED
for thaT over aNd oVer AgaiN

\- we HaVe eXaCT coNTrOl aND veRsion how ThE eNviroNmenT LOOKs liKe.

\- REsouRces aRe better distrIbuTed tHAn iN hardWare vIrtuAlIzatiOn
enviRonmeNtS

#2 Is a pet project oF minE, a backend For A mObiLe app. ThERe are sTilL biG
parts mIssing, bUT in ThE MOMeNt it consists of a bacKeND ApPlicatioN which
EXpOsES a REST APi rUnnIng oN EQuinoX pluS A dAtabase (iN an own COnTaIner).

The ReAsons I SeE foR usIng doCKer hEre:

\- I haVe controL and vERsioning of the eNVironment

\- I can TEsT ON mY LaptOp iN the same comPoneNTs as Prod, BUt ScaLEd dowN (by
juSt SPiNNing up the database anD oNe backEnd coNtainer)

\- Since mOre and more CLOUd providErs aRE sUPporting Docker (i am cuRrently
havINg an eye oN AWS aNd DigitaLOcean, havEN'T decided Yet), SwiTchIng THE
pRovider in the fUTUre wIlL be easiEr cOmpared To hAviNg, sAy a PrOprietary
Image or wHaTeVeR.

\- IF I eVer scALe up the pOjEct AnD onBoard NEw teamMembeRs, thE eNtRY
baRriers fOR (aT LEast) HeLpIng iN OpS wIll be LoweR ThaN if they Have to
leaRn tHE sinGlE tEchnoloGies until they GeT at least baSiC knOwledgE OF the
projEct.

------
rcconf
My apologies if I'M HijackiNg tHe oriGinaL poster.

DoEs DOcker hAndLE multi-EnviroNment CoNfiGURatioN MAnAgeMeNt? For exampLE:
Qa, sTage aNd Live Have the Same config files, but DIffErent values.

CuRreNtly WE'Re UsiNG ANSibLe ANd wE SEt variables for a Specific enViROnMent,
then we FEed ThOse variAbles inTo conFIg files Based on whEre we're dePlOyinG
TO (coNfig files aRe not dupLicated, onLY variABlEs thaT feEd into CoNfiG
fileS.)

All of OUr cOnfigUratioN iS in git And we CaN quickly See and change it.

How
 apsects
osipov mentioned: 

#1 is in  my d ayj ob: 
We u se d ocker in combi n atio n with vagrant for spi nning  u p  a t e st  envi ronment co n s ist in gofse v er al co nta iners w ith differ ent  c omponents (b o th  ur own
pr odu cts and 3rdpar ty) to  r uni ntegr ati on te sts ag a inst t hem.

The  m a in rea s ons for t hi s ap proach are: \- We ca n  supply contai ners w it h  t h e 
in sta lled produ cs  whic h  savest im e o n a u tomated runssince you d o n't  haveto 
ru n  a set up ev er y  ti me

\- We c an p rovide ce rtainc ustomiz a tions w hich a reonl y ne e de dfor  t e sti n gand whi ch we do n' twantto s h i p to c ust omer s wit hout doing al l t he s t eps  need ed
fo r th at  over  and o ver a ga in

\- We haveexac t control  an dver si on ho w  the e nvi ron ment lo oks lik e .
\- R e so urces are better d is t r ib uted tha n in h a rd wa r e virtua li zat ione n viron ment s 
#2 Is apet pr o je ct  of min e,  a bac ke ndfor  a mo b ileApp. T here are  stil l  big
parts mis s ing, but in t h em o me n t it  co nsists of a  bac k endappl i ca tio n  whic h
exp os e sa  REST API running o nequino x plu s a database(in an own c o ntainer) .

T h er easons I see f or us ing docker here:

\ - I h ave cont rol and v e r sioningofthe  en vir o n me nt

\- I cant e st o nmy lapt opin thesam e c omp one nt s as prod , but sc al ed  d ow n ( by
ju s t spinni ng  up  t hedatab a se and  oneback en dc ont ainer)\- S ince  m or e an d m or e clo ud p r ovi ders ar e support ing Dock er  ( I am cu rrently
havin gan eye onAW S a nd Dig i t alOcean,  haven't decided yet),s witchin g t he
pr ovid er in the  fu ture w ill be eas ier co mpare dtoh a ving, s ay  apr oprietaryi m age  or w ha teve r.

\-If I ever scale up the  poject and o nbo ardn e wtea m me m ber s, the e ntry
barriers f or (at lea st )  h elping inO pswi ll be l ower th an if they ha ve to
lea rn the si ng le t e c hno logies unt il theyget at le a st ba s ic  know led ge ofth e
p rojec t.

-- - --- 
rcco nf
Myap ologie s ifI' m hijack ing the original poster .

Doe s Doc ker  handle m ult i -en vironment  con figuration  ma nag ement ? F o r exa mple : 
q a,s tageandl ive havet he  sa m e  c onfig files , b utdiffe ren t  value s.
Currently we're u s ing Ansible an d we s etvar i able sfor a specific  en vi r o nment,
t he n we feed t hose var ia b les i nto co nfig f iles ba s e do n wher e we 're  deployin g
t o( configfi le s  are n ot d up licate d, onl y  var i a bles that feed i nto c o n fig
f i les .)

A ll  of our conf igurationis in git a nd wecanquick ly seean d chan geit .

How
 apsects
osipov_mentioned:

#1 is_in my dayjob:

We use_docker in_combination_with vagrant_for_spinning up a_test environment
consisting of_several containers with different_components (both ur_own
products_and 3rd party) to run integration tests against them.

The main reasons for this approach_are:_\- We_can_supply_containers with the
installed producs which_saves time on automated runs_since you_don't have to
run a setup every time

\- We_can_provide certain customizations_which are only needed for testing and
which we don't_want to ship to customers without_doing all the_steps_needed
for_that over and over_again

\- We have exact control and_version how the environment looks like.

\-_Resources are better distributed than in hardware_virtualization
environments

#2 Is a pet project of_mine, a backend for a_mobile App._There are still big
parts missing,_but in the_moment it_consists of a_backend application which
exposes a REST API_running on equinox_plus a database (in an own_container).

The_reasons I see_for_using_docker here:

\-_I have control_and_versioning of_the_environment

\- I can test on my_laptop_in the same components as prod, but_scaled down (by
just spinning_up_the database and one_backend container)

\- Since more and_more cloud providers are supporting Docker_(I am_currently
having an_eye on AWS and DigitalOcean, haven't decided yet), switching the
provider in_the future will be easier compared_to having, say a_proprietary
image or_whatever.

\-_If I ever_scale_up the_poject and onboard new teammembers, the entry
barriers_for (at_least) helping in Ops will be_lower than if they_have_to
learn the single technologies until they_get at least basic knowledge of_the
project.

------
rcconf
My apologies if I'm hijacking_the_original_poster.

Does Docker handle multi-environment configuration_management? For example:
qa, stage and live_have the same_config files, but different values.

Currently we're using_Ansible_and we set variables for a_specific_environment,
then we feed those variables into_config_files_based on where we're deploying
to_(config files are not duplicated, only_variables that feed into config
files.)

All of our configuration is_in git and_we can quickly see and_change_it.

How