瞧瞧這精美的 rake app:deploy

完成 rack cluster 之後，總算又完成 daemon cluster.
拜 ruby 亂七八糟的 thread/process 之賜。
真詭異，Thread.new 沒事，Process.fork 倒是會出事...
facebooker 大概也沒有 thread-safe 吧？而且到底幾時才要出新 gem???

我在想，到底是 ruby solution 都要這樣老是有問題，
還是我最近狀況真的太糟，所以一直捅簍子？？
有時候真的覺得很氣餒......

photos@v95 ~ $ rake app:deploy
(in /home/photos)
Resetting...
No local changes to save
HEAD is now at f7b154d... added daemon control in app:server. moved all proj-specific to my:...
Sending TERM to thin(9207)...
Killed thin(9207)
Starting thin on 0.0.0.0:3500...

Sending TERM to thin(9210)...
Killed thin(9210)
Starting thin on 0.0.0.0:3501...

Sending TERM to thin(9213)...
Killed thin(9213)
Starting thin on 0.0.0.0:3502...

Sending TERM to thin(9216)...
Killed thin(9216)
Starting thin on 0.0.0.0:3503...

Sending TERM to thin(9219)...
Killed thin(9219)
Starting thin on 0.0.0.0:3504...

Sending TERM to thin(9222)...
Killed thin(9222)
Starting thin on 0.0.0.0:3000...

Sending TERM to thin(9225)...
Killed thin(9225)
Starting thin on 0.0.0.0:3001...

Sending TERM to thin(9228)...
Killed thin(9228)
Starting thin on 0.0.0.0:3002...

Sending TERM to thin(9231)...
Killed thin(9231)
Starting thin on 0.0.0.0:3003...

Sending TERM to thin(9234)...
Killed thin(9234)
Starting thin on 0.0.0.0:3004...

Sending TERM to (9237)...
Killed (9237)
Starting #0 ruby daemon/bin/cron.rb...

Sending TERM to (9240)...
Killed (9240)
Starting #0 ruby daemon/bin/sync.rb...