Thanks for the reply. I understand the best practice of 1 repo == 1
project. But sometimes it just doesn't make sense. For example, I
have another big rails app that is not ready for deployment yet, but
I'd like to display a semi-functional splash site that uses lots of
the same assets. So I
On Thu, Jan 15, 2009 at 11:44 AM, Henry hpoy...@gmail.com wrote:
...I have another big rails app that is not ready for deployment yet, but
I'd like to display a semi-functional splash site that uses lots of
the same assets. So I have a one-file sinatra app sitting in another
directory in
On 15 ene, 18:44, Henry hpoy...@gmail.com wrote:
Thanks for the reply. I understand the best practice of 1 repo == 1
project. But sometimes it just doesn't make sense. For example, I
have another big rails app that is not ready for deployment yet, but
I'd like to display a semi-functional
