Doug Jolley wrote:
>> Why do you need this system rather than just pulling down the latest
>> version from source control ?
>
> Because there are some files that may have been modified with customer-
> specific code. We never want to overwrite these files. However, if a
> file in this group does
On May 3, 5:14 pm, Michael Pavling wrote:
> I'd suggest a review of your internal processes with all the
> developers, PMs and other stakeholders to discuss how to manage code
> deployment. As a suggestion, I'd recommend a branch of your code for
> each of your deployed client sites. Using Git/Mer
On 3 May 2010 17:02, doug wrote:
>> Why do you need this system rather than just pulling down the latest
>> version from source control ?
>
> Because there are some files that may have been modified with customer-
> specific code. We never want to overwrite these files. However, if a
> file in t
> But if you *must* do something like the above, it's called `rsync` and
> it handles case #3 as well.
I'm going to look into this. Thanks for the suggestion.
... doug
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to
> Why do you need this system rather than just pulling down the latest
> version from source control ?
Because there are some files that may have been modified with customer-
specific code. We never want to overwrite these files. However, if a
file in this group doesn't exist on the system being
On May 1, 2:13 am, doug wrote:
> I have deployed several instances of a Rails application. I am now
> considering how I might apply application updates to each of the
> various instances. I would like the updates to be contained in some
> sort of an archive like a tar archive. There are two t
6 matches
Mail list logo
