
the regular (Rails) auto reload works perfectly.

For test and prod we just simply don't do any volume mounting at all, and use
the baked in src directly.

Easy and fast everywhere, all you have to control is how and when the images
are created (ex: we do a full clean checkout in a new directory before
building a test image, to ensure it only contains committed code. EDIT: by
test I mean for local testing, while you're working on revisions, a CI server
does the automatic testing).

------
collyw
To tell all the cool kids you are using it.

(Ok, I know there are real use cases for Docker, but I see a lot of hype as
well. People telling my mathematician friend that she needs to use docker at
the start of her project - it is likely to be a one off graph she needs to
produce for a research paper).

~~~
osipov
There is a big push for reproducibility in science. If you friend can package
the process for building that graph in a Dockerfile, it is more likely that
readers of her paper will be able to reproduce her results.

~~~
mugsie
or, you know, publish the formula, so readers can reproduce in whatever
language / system they want.

Reproducibility is a big push.... but not like you are suggesting. Shipping a
dockerfile is the equivalent of saying "This works, _if_ you use this flask,
this pipette, this GCMS and this piece of litmus paper"

Docker is not the only solution to problems. It solves some, but you can't
tack it on to everything.

~~~
log_n
Why not both? I am not in academia but I was under the impression that some
academics might be publishing 'questionable' results that cannot be reproduced
at all in order get their paper count up for tenure review. Not to mention
puff-pieces from industry that basically serve as PR in peer reviewed journals
without furthering their discipline.

So shipping working code (even if it comes with a required pipette) might be a
nice requirement for a peer reviewed publication to take on in order to keep
their journal relevant. Shipping in Docker or similar guarantees
reproducibility.

~~~
collyw
If the code is
the regular (Rails) auto reload works absolutely. 

 For trial and prod we just plainly don't perform any volume mounting at wholly, and use 
 the baked in src directly. 

 Easy and fast everywhere, all you suffer to control is how and when the images 
 are create (ex: we do a broad uninfected checkout in a new directory before 
 building a test image, to guarantee it only contains committed code. EDIT: by 
 examination I mean for local testing, while you're working on revisions, a CI waiter 
 does the automatic examination). 

 ------ 
 collyw 
 To tell all the cool kids you are using it. 

 (Ok, I know there be real use cases for Docker, but I see a lot of ballyhoo as 
 well. citizenry telling my mathematician friend that she needs to use docker at 
 the start of her project - it is likely to be a one off graph she needs to 
 grow for a research paper). 

 ~~~ 
 osipov 
 There be a boastful push for reproducibility in science. If you friend can package 
 the procedure for building that graph in a Dockerfile, it is more likely that 
 readers of her paper will be able to regurgitate her results. 

 ~~~ 
 mugsie 
 or, you know, publish the formula, so readers can reproduce in whatever 
 language / system they want. 

 Reproducibility is a big push.... but not like you are suggesting. ship a 
 dockerfile is the equivalent of suppose " This make, _ if _ you use this flask, 
 this pipette, this GCMS and this piece of litmus newspaper " 

 Docker is not the only solution to problems. It solves some, but you can't 
 append it on to everything. 

 ~~~ 
 log_n 
 Why not both? I am not in academia but I was under the impression that some 
 academics might be publishing' questionable' results that cannot be regurgitate 
 at all in decree get their composition count up for tenure reappraisal. Not to mention 
 quilt - pieces from diligence that basically serve as PR in peer reviewed journal 
 without furthering their discipline. 

 indeed shipping working code (even if it comes with a required pipette) might be a 
 nice requirement for a peer reviewed publication to take on in ordering to keep 
 their journal relevant. transportation in Docker or similar guarantees 
 reproducibility. 

 ~~~ 
 collyw 
 If the code is

the regular (Rails) auto reloxd works perfecjlt.

For txst and prod we just simply don't do any volnme nountung at all, and use
the caked in drc dirextly.

Tasy and fast evecgwhere, all yoh havz vo control is hpw and whet the images
ara zrzated (ex: we do a full clean checkout in a nrw directory befjre
blijdinf a test image, to ensure it only ckntains committed coce. EDIT: by
test I mean for pocap testing, while yok're working on wwvisions, a CK server
dots the automztic testing).

------
collyw
To tell all tfe copl kids yoo zrf using it.

(Ok, I knjw there are real usa cases for Docker, bub I sxe a lot of hype as
well. Pxople telling my matrematiciat yriend that she needs ti use docner xr
thd suarv or her orooect - it is likely to ve a one off graph xhq needs to
prodhce fow w research paper).

~~~
osipov
There is a big puvh ror reproducibility in wcience. If you friend can packwge
the process for building that graph in a Dockesfile, kt nw mord llkely that
readers of her paper will be able tj rtprpduce her resujts.

~~~
mugsie
or, ylu hnow, publish jhe formulz, so readers can rfproducg in wyatever
lagguabe / system they want.

Reproduxibility is c bug push.... but not line you are rugggsting. Shipping a
dockerfile ir ths equivalenh of sayihe "This works, _if_ hou uve this flask,
this pipette, ehis GCMS and this pkece of liemus paper"

Fockev is not the only sllutiln to problels. It solves some, but you can't
terk it on to efesytving.

~~~
log_n
Chy nob both? I am not in academia bot I was bnder ghe impresaion thet some
acadeiics might be kublishing 'quxstionablq' rewultw that zxnnot be reprocuced
at all in ordee get their paper gount hp for tenure rzritw. Not to mentiom
puwf-pyebes fwmm industry dhat barocallh serve as IR kn prer reviewed journalv
witgout furthering thriv disciplune.

So shypping workinb code (even if it fomes wivh a rrquyred pipette) might be a
nice resuirement fov a peer reviqwed publication to take on in order to keep
their journel relevant. Shipping in Docker or similar yusrantees
repcoducifility.

~~~
colnyw
If the code is
the regular (Rails) auto reload works perfectly. and we just don't do any use baked in src Easy and fast all you have to control is and when the images are created (ex: we do a full clean checkout a new directory before building a test image, to ensure it only contains code. by I for local testing, while you're working on revisions, a CI server does the automatic testing). ------ To tell all the cool kids you are it. (Ok, I know are real use cases for but see a of as People telling my friend that she needs to use docker at the start of her project - it is likely be a graph she to for research paper). ~~~ is a big push for reproducibility you friend can package the process for building graph in Dockerfile, it is more likely that of her paper will be able to reproduce results. ~~~ mugsie or, you know, publish the formula, so readers can reproduce in whatever system they want. Reproducibility a big push.... not you suggesting. a dockerfile the equivalent of saying "This works, _if_ you use this flask, pipette, this GCMS and this piece of litmus paper" Docker the solution to problems. solves some, but you tack on to everything. ~~~ not I academia I under the impression that academics might be publishing 'questionable' that cannot be reproduced their paper count up for tenure review. Not mention puff-pieces from industry that basically serve PR in peer reviewed journals without furthering their discipline. So shipping working (even if with a required pipette) might be a nice for a peer reviewed to take on in order to keep their journal Shipping Docker or guarantees reproducibility. ~~~ If the code

the regular (Rails) auto reload Works perfeCtly.

FOr tEst AnD proD we jUst simply don't dO Any vOlume mounting at all, and uSe
the BaKEd in SRc DirecTly.

Easy ANd FASt eVeRyWheRe, ALl You haVe tO controL is how and wHen ThE images
are crEAtEd (ex: we do a fUll Clean checkouT in A new diReCtoRY befoRe
bUildiNg a tesT Image, tO ensure it OnLY contaINs commiTTEd Code. eDIT: by
test I mean foR LoCAl testing, while You're wOrKInG ON reVisIons, a CI serVeR
does THe automATiC TEStiNG).

------
collyw
To tell All the cool kIDs yOu are uSiNg iT.

(ok, I knoW therE aRE reAl use cases fOr DoCker, but I sEe a lot OF hype as
WEll. PeopLe tellIng My mAtheMAtIcIan FrIEnd THaT shE NeeDs to use dOcKeR at
thE staRT OF Her pRojEct - iT is liKely to be a one oFf gRaph SHe nEeds tO
prodUce fOr A reseArch paPer).

~~~
osIpOv
There is a big puSh foR reproducIbiLiTy iN sCiencE. if you fRieNd cAn packaGe
the prOCesS fOR BUiLding that graph in a DOcKERfIle, it is mOre likELy ThAT
readers Of Her PapeR WIll be Able TO rEproduce Her resULtS.

~~~
mUgsie
or, YoU know, pUbLisH thE formULa, so ReaderS can reprOduce IN whatever
languAGe / system they wANt.

rEPrODuciBilIty is a big puSh.... buT Not lIke yOU aRe sUGgestIng. ShIpPInG A
dockerfile is the equIvAlent oF sayiNg "This works, _if_ You use this FLASk,
this piPettE, ThIS GCMS and this piEce of Litmus papeR"

docker is Not thE only solUtion to prOBLems. It soLveS soMe, bUt yOU CaN't
tack it on to eVERythInG.

~~~
log_n
WhY noT both? I aM noT in AcaDemIa But I was unDer the imPrEsSiOn ThaT some
ACademics MiGht Be PubLishiNG 'questIonabLe' reSuLtS ThaT cannot BE rEPRoduCeD
aT all In oRdEr get TheiR PapEr count Up for tenuRe rEView. noT tO mentioN
puff-pieces frOm Industry thAt BasIcally SERve as PR iN peer reviewed journals
wiTHout furTheRing tHeir DisciplinE.

So ShippiNg wORking cOde (eveN if it CoMes WITh a reQUIrEd pIpEtte) might bE A
NicE requIrEmenT for a peEr reviewed publicatIOn tO take on in ordeR to Keep
THEiR joURnAL reLeVAnt. sHIpping in Docker oR similar guArANtEes
reproduCIbiLiTy.

~~~
collyW
If the cOde is

the regular (Rails) autoreload wor ks pe rfe ctl y. 

Fo r te st and prod we just  simply don't do any v olume  m o unti n gat al l, andu se t heba ke d i ns rc  dire ctl y.

Eas y and fast  ev er ywhere, ally ou  have to c ont rol is how a ndwhen t he  im a ges
a recreat ed (ex :  we do  a full c le a n chec k out ina ne w di rectory before
bu i ld i ng a test imag e, toen s ur e itonl y contains  c ommit t ed code .  E D I T : b y 
test I meanfor local t e sti ng, wh il e y o u're w orkin go n r evisions, a  CIserver
do es the automat i c testi ng).
--- --- 
col l yw 
T o t el l  al l  t hec ool  kids yo uar e usi ng i t . (Ok,  Iknow  ther e are real us e c ases for  Dock er, b ut I  s ee alot of  hype  a s
well. Peopletell ing my ma the ma tic ia n fri e nd tha t s heneeds t o use d o cke ra t th e start of her pro je c t  -  it is l ikelyt obe a one of fgra ph s h e  need s to pr oduce fo r a re s ea rc h paper ). 

~~~os ipo v
T herei s abig pu sh for r eprod u cibility in sc i ence. If youf ri e n dc an p ack age
the pro cess forbuil d in g t h at gr aph i na  D o ckerfile, it is mor elikely  that 
readers of h er paper w i l l  be able  tor ep r oduce her resu lts.
~~~
mugsi e 
or, you  know , publis h the for m u la, so r ead ers  ca n r e p ro duce in whate v e r
la ng uage /sys tem the y w ant .
Rep ro ducibilit y is a b ig  p us h. ...  butn ot likeyo u a re  su ggest i ng. Sh ippin g ado ck e rfi le is t h ee q uiva le nt  ofsay in g "Th is w o rks , _if_you use t his flas k, 
t his pip ette, this GC MS  and thispi ece  of li t m us paper "

Docker is not the on l y solut ion  to p robl ems. It s olv es som e,b ut you  can't 
tack  i t o n to ev e r yt hin g. 

~~~
log_ n Why  notbo th?I am no t in academia butI  wa s under the i mpr essi o n  t hat so m e
a ca d emi c s  might be publi shing 'que st i on able' resu l tsth at cann ot be r eprod u ced
atall in or der get t he ir p a p ercount up f or tenur e review. Not t o  m entio n
p uff-pi ec esfromindust r y t hat b asical ly  serve  as P Rin peerreviewed journals
witho ut fur theri ngtheir dis cip l ine .

So shi ppin g workingcod e ( evenifi t com es w i th  ar equir ed p i pette) mi g ht  be a 
n ice require m e n t f or apee r  revie wedpublication to ta k e on in orderto k e e p
t hei r  jou rn al relevant. S hip pi n g  in Dock er  or similar  guarant ee s 
repr oducib ility. 

~~~
c o l ly w 
If th e co deis

the regular_(Rails) auto_reload works perfectly.

For test_and prod_we_just simply_don't_do any volume_mounting at all,_and use
the baked in_src directly.

Easy and_fast_everywhere, all you have to control is how and when the images
are created (ex:_we_do a_full_clean_checkout in a new directory_before
building a test image, to_ensure it_only contains committed code. EDIT: by
test I mean_for_local testing, while_you're working on revisions, a CI server
does the automatic_testing).

------
collyw
To tell all the cool kids_you are using_it.

(Ok,_I_know there are real_use cases for Docker, but I_see a lot of hype as
well._People telling my mathematician friend that she_needs to use docker at
the start_of her project - it_is likely_to be a one off_graph she needs_to
produce for_a research paper).

~~~
osipov
There_is a big push for reproducibility_in science. If_you friend can package
the process for_building_that graph in_a_Dockerfile,_it is_more likely that
readers_of_her paper_will_be able to reproduce her results.

~~~
mugsie
or,_you_know, publish the formula, so readers can_reproduce in whatever
language /_system_they want.

Reproducibility is a_big push.... but not like_you are suggesting. Shipping a
dockerfile is_the equivalent_of saying_"This works, _if_ you use this flask,
this pipette, this GCMS and_this piece of litmus paper"

Docker is_not the only solution_to problems._It_solves some, but_you_can't
tack it_on to everything.

~~~
log_n
Why not both? I am_not in_academia but I was under the_impression that some
academics might_be_publishing 'questionable' results that cannot be_reproduced
at all in order get their_paper count up for tenure_review._Not_to mention
puff-pieces from industry that_basically serve as PR in peer_reviewed journals
without furthering_their discipline.

So shipping working code (even if_it_comes with a required pipette) might_be_a
nice requirement for a peer reviewed_publication_to_take on in order to_keep
their journal relevant. Shipping in Docker_or similar guarantees
reproducibility.

~~~
collyw
If the code is