> Don't quote something out of context.
>
> I deliberately removed that before replying, so you assumed
> that I was talking about that now? I am well aware what SVN
> is, and anyone who has read the documentation would know that
> without a doubt now wouldn't they?
I don't see any reason to doubt you know what SVN is. You may well know it
better than I do. But I didn't quote anything out of context. I simply
replied to your response to Jochem, without referring to any other email in
the thread. I apologize in advance for what will certainly be difficult to
read, but here's Jochem's post to you:
"Andrew Scott wrote:
> What
> Do you mean by repo -> server and server -> repo?
>
> The latter should never be an issue, or even considered. Anyone
who makes
> changes to production and not in a development environment shouod
be hung
> out to dry or better still beaten with a stick until you realise
that
> development is what it means.
So you think the entire /etc/ folder on a production box is the same
as
an /etc/ folder on a development box? You think they have the same
hostnames? The same IP addresses? The same firewall rules? That the
test
environment has a two year backup retention like production has?
Not everybody uses SVN just for sourcecode. Some use it for their
university thesis. Some for their grocery list. Some use SVN for
complete server configurations. And what you use it for does
influence
the usage pattern. It is perfectly acceptable to change the
-Dmail.host
oarameter in your jvm.config file directly on production and then
back
it up to SVN.
> Once you have deployed to a production server, it should never
have any
> ties with the repository in any way shape or form. If you are one
of
> those that think this is ok, then you will need to adopt new
procedures
> quickly. Before you adopt bad and I mean VERY BAD ideas.
Generally speaking you don't want to have production running
directly
from a working copy. But there is nothing wrong with putting $Id$,
$HeadURL$ etc. in your sources so that code and configuration files
on
the production box points back to a specific version of a file in a
repository."
Reading that, my interpretation is that you stated that copying from your
production server to a repository was never acceptable. Jochem then
presented a scenario where he believed it was acceptable. I tend to agree
with him in this case, for what that's worth.
You posted this in response:
"Don't put words into my mouth.
As for xml changes that are not related to your source code is
generally
handled by daily backups anyway, and most people prefer that as it
can put
the machine into a state quicker than your method. But hey thats
your choice,
you want to create extra work for you then go for it.
As for the actual content of the source files, DID I EVER MENTION
ANYTHING
about that?
NO, I did not and I wouldn't like to have you tell me otherwise."
Now, as I stated before, I don't see where he put any words in your mouth.
You clearly state that it's unequivocally a VERY BAD idea to copy from a
production server to a repository, and he says otherwise.
> Why is that Dave?
>
> Because the examples in the documentation relate to what you
> made an assumption on.
>
> If you want to be corrected, I actually referred to the files
> and their contents from SVN. I never brought that up..... And
> yet it was referred to as if I had.
Again, I don't see where he implies that you said anything about the
contents of files. He says something about the contents of files, though, as
a justification for having files on the production box point to specific
copies in a repository. Clearly, that would be a "tie with the repository",
which you clearly stated would be a VERY BAD idea.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
Fig Leaf Software provides the highest caliber vendor-authorized
instruction at our training centers in Washington DC, Atlanta,
Chicago, Baltimore, Northern Virginia, or on-site at your location.
Visit http://training.figleaf.com/ for more information!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to
date
Get the Free Trial
http://ad.doubleclick.net/clk;203748912;27390454;j
Archive:
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:310799
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
