July 28, 2014
7:34 a.m.
We've been bitten a few times at Ta Mère by the problem of changing metacello configuration. At the moment, we rely on the policy of "you should never change a Metacello version once it has been published". Of course this is fragile and we've ended up with different code loaded in different environment while we were expecting stuff to be identical. Has anyone already tempted to centralize configurations/package in a read-only place (S3? Azure Storage?). Something like RubyGems or similar. It may be completely stupid to have centralised system but I'm not satisfied with the infastructure supporting our configurations. Am I the only one having this problem? How do you handle it?