Hi all,
David Kelly <[email protected]> Dec 19 09:20AM -0600 ^
> I'm not using SVN to maintain production file `in situ`.
If you heard what I've been saying between the lines, you *should*.
Let svn be your remote file sync mechanism.
> Files exist at 3 different places: in production (on the server),
in the repository, and in my working copy. When I'm working on a
server, I make changes in various files, or create new ones, I wait
few hours or few days to make sure everything works fine, then I
don't always remember what files have changed.
If the files were under svn then status, diff, or commit, will tell
you which ones have been changed since the last commit.
So basically, you say I should turn my /boot, /etc and /usr/local/etc/
into working copies and clutter them with .svn directories? And what
about the 30 or 50 text files and 150MB of binary files that live here
and are not under version control?
You need to study the use of forks. Thinking you need a "beta" fork
to run in parallel to your head "working copy" which will be very
much like the difference between FreeBDD -CURRENT and -STABLE.
I really don't see the point, unless I'm supposed to change the
current fork in production every now and then.
If I understand correctly:
- I turn /boot, /etc, /usr/local/etc into working copies
- each one follows the "beta" fork
where is my "head" fork? Why do I have a "head" fork anyway? May be
I'm missing something here, but forking looks really overkill for my
needs.
Perhaps each server has a customized version of the config files?
Then there is another fork.
Yes they have. They have nothing in common, except the "freebsd 8.1"
part. They serve very different purposes, on very different networks.
For now, I use a single working copy, with a directory for each host.
Simple enough.
Rich Siegel <[email protected]> Dec 19 10:29AM -0500 ^
On Sunday, December 19, 2010, Patrick Proniewski <[email protected]>
wrote:
>remember what files have changed. Comparing manually the production
>directory tree and the working copy is a very painful and long
>process. I want to make that automatic.
At this exact moment, your best bet is probably to use something
like ExpanDrive to mount your remote server via ssh as a file
system; then you can use "Find Differences" to compare your
local directory with the server. Do note that MacFUSE+ssh (of
which ExpanDrive is one implementation) will perform very
slowly; but for this purpose it should serve.
I've given this option a though, earlier, but dismissed the idea. I
don't want to add a kernel module on every Mac I'm working on, just
for that purpose.
I think that the points about changing your workflow are well
made, since the way you've described it today, your workflow is
calculated to drive you nuts, but that's really a different
issue. :-)
I'm not driven nuts yet ;)
And my workflow would be very nice if I had the ability to compare
remote/local directories the way I can compare local/local directories.
David Kelly <[email protected]> Dec 19 10:57AM -0600 ^
NFS on FreeBSD works well with MacOS. Shares a lot of the same code.
However, I grimace at even suggesting an NFS export from a public
web server over the internet without an encrypted VPN tunnel.
NFS could be ok. And I'm pretty sure I can make a launchd plist to
handle ssh tunnel creation on demand to access a remote NFS behind a
firewall via an encrypted connection. I've done that quite often with
other protocols (usenet, mysql, vnc, apple remote desktop, ...)
BBEdit can browse a remote directory tree via an ssh connection, too
bad it can't natively use the same transport to make directory tree
comparisons :/
Ron Catterall <[email protected]> Dec 19 11:12AM -0600 ^
Just a thought - would Interarchy do the job?
May be the net disk feature would work, yes. But if I can do it for
free with NFS/ssh-tunnel it's better.
thanks,
patpro
--
You received this message because you are subscribed to the
"BBEdit Talk" discussion group on Google Groups.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
<http://groups.google.com/group/bbedit?hl=en>
If you have a feature request or would like to report a problem,
please email "[email protected]" rather than posting to the group.
Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
