ã¯ããã« ãã®è¨äºã¯GREE Advent Calendar 2013å¹´ã®21æ¥ç®ã§ããã楽ãã¿ãã ããï¼ ããã«ã¡ã¯ãã¢ã´ã²ãããã³ãã£ã¼ã ã¨è©å¤ã®ä¹å²¡ã§ããGREEã§ã¯ãJavaãScalaãå¸æããããã®åå°ãåºããããããããã¤ãç£è¦ã®ä»çµã¿ã¥ãããªã©ã横æçã«ãã£ã¦ãã¾ããä»åã¯ãã®éç¨ã§å¾ãããç¥èããCapistrano 3ã®å ¥éè¨äºãã¨ããå½¢ã§å ±æããã¦ããã ãã¾ãã ãã®è¨äºã§ã¯Capistrano 3ã®åºç¤ããç´¹ä»ãã¾ããCapistrano 3ã¯Rubyããã¼ã¹ã«ãããµã¼ãæä½ããã³ãããã¤ã®èªååãã¼ã«ã§ããCapistrano 3ãå©ç¨ãããã¨ã§ããããã¤ãªã©ã®è¤éãªãµã¼ãæä½ãèªååãããã¨ãã§ãã¾ããããã®è¨äºã§ã¯ãç¹ã«ãããã¤ã«ç¦ç¹ããã¦ãªãããCapistranoã§ãµã¼ãæä½ãèªååããèãæ¹ã¨å®ç¾æ¹æ³ãã説æãã¦ããã¾ãã Capistrano 3ã®ç¿å¾
Up until lately I was happy using Capistrano for my deployments. But then I noticed the following: Capistrano was utilizing 70 % of a physical CPU core when deploying on the go. I'm on a dual core system so this impacts my Mac Book Pros overall performance, battery life and it kept me waiting for a long long time. My iPhone was at edge speed so I figured Capistrano spent most of the time waiting f
æ¬é£è¼ã®ç¬¬1åãã第3åã¾ã§ã¯ã主ã«moonlinxã®ã¤ã³ãã©æè¡ã説æãã¦ãã¾ãããä»åããã¯moonlinxã®ã¦ã§ãã¢ããªã±ã¼ã·ã§ã³æè¡ã«çç®ãã¦è§£èª¬ãã¦ããããã¨æãã¾ãã ãããã¤ãã¼ã«ãCapistranoãã®é å ã¦ã§ãã¡ãã£ã¢ãmoonlinxãã§ã¯ãmoonlinx Membership Centerã¨å¼ã°ããã¯ãªã¨ã¤ã¿ã¼åãã®ç»é²å¶ä¼å¡ãµã¼ãã¹ãéå¶ãã¦ãã¾ããããã¯ããã¶ã¤ãã¼ãé³æ¥½æ´»åãè¡ãã¢ã¼ãã£ã¹ããã¿ã¼ã²ããã¨ãããµã¼ãã¹ã§ãããã¯ãªã¨ã¤ã¿ã¼èªèº«ã®æ´»åãããã¢ã¼ã·ã§ã³ãããã¼ã«ã¨ãã¦æ´»ç¨ã§ãããµã¼ãã¹ã§ãã ãã®Membership Centerã§ã¯ããã¬ã¼ã ã¯ã¼ã¯ã¨ãã¦Ruby on Railsãå©ç¨ãã¦éçºãã¦ãã¾ããã¾ããPhusionã®Passengerãå©ç¨ãã¦ãApache2ä¸ã§åä½ããã¦ãã¾ãã Railsã®éç¨ç°å¢ã¯ãMongrelã¨Mongre
ã©ã³ãã³ã°
ã©ã³ãã³ã°
ã©ã³ãã³ã°
ãªãªã¼ã¹ãé害æ å ±ãªã©ã®ãµã¼ãã¹ã®ãç¥ãã
ææ°ã®äººæ°ã¨ã³ããªã¼ã®é ä¿¡
å¦çãå®è¡ä¸ã§ã
j次ã®ããã¯ãã¼ã¯
kåã®ããã¯ãã¼ã¯
lãã¨ã§èªã
eã³ã¡ã³ãä¸è¦§ãéã
oãã¼ã¸ãéã
{{#tags}}- {{label}}
{{/tags}}