What would be cool is if CF Administrator had a plugin to various SCM's
which lets you assign a SCM type, server, login, password, etc, and be
able to manage deployments from there.   

-----Original Message-----
From: Russ [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, August 02, 2005 1:54 PM
To: CF-Talk
Subject: RE: CFEclipse and FTP (was: MM and CFEclipse)

We use ftp for developing on the dev server, which is a checked out copy
of the production code (which is checked out both on the production
server and the dev server).  When I'm ready to deploy, I check in the
files I want to deploy, and do an update on the production server.  We
use Subversion and TortoiseSVN.  

It's probably not a perfect solution, but it sure beats ftping files
over.
It's still a work in progress, and we're constantly looking for ways to
improve it.  If anyone has any suggestions, I would appreciate it.  

Russ

-----Original Message-----
From: Katz, Dov B (IT) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 02, 2005 1:48 PM
To: CF-Talk
Subject: RE: CFEclipse and FTP (was: MM and CFEclipse)

Barneyb, sorry, I wasn't too clear.

I have a home-based Source Control Server.

When developing , I check in and out of it.  I cut and branch releases,
etc.

My structure looks like this  /websites/domain/(www, database,
private,etc)/files

On my web server, I have sites which map their roots to an export  of
/websites/domain/....

Then I can sync them on staging. And once I'm ready, sync them on
production.

The syncing mechanism is all command-line based, so I wrapped that up in
a CF app so I can deploy it via hitting some URLs' ...   Only changed
and new files are moved (and deleted ones are removed).  

In CVS parlance, I do a cvs update, etc... In perforce, it's a p4 sync
on a given clientspec.

Since I only have 2 prod servers, its not a big deal, but you're right
that its not scalable should my server farm grow.

This is for a personal/private website project, not work-related, and
I'm the only developer, so I'm not too concerned at the moment about
making it too much more complicated...


-Dov

-----Original Message-----
From: Barney Boisvert [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 02, 2005 1:31 PM
To: CF-Talk
Subject: Re: CFEclipse and FTP (was: MM and CFEclipse)

If you pull right from your source control system to your production
webroot, make sure you're either doing an export (not a checkout), or
you're masking your metadata directories in some fashion (i.e. with the
web server).  There's data in there that you don't want to be public.
If you have to do it that way, I'd recommend the latter, as doing
repeated exports just chews up bandwidth unnecessarily (since without
the metadata, you can't do deltas).

Much better (at least in my opinion) is to have your production systems
directly mirror you staging system.  That staging system keeps an
up-to-date copy of the codebase from version control, and then uses some
delta-aware transmission method (I like rsync) to keep all the
production servers in sync with it, except for the metadata directories.
It also absolves you of having to log into each production server to
pull code updates, which is a huge pain if you've got more than a couple
machines.  Having a central point that you can push from is a lot
easier.

cheers,
barneyb

On 8/2/05, Katz, Dov B (IT) <[EMAIL PROTECTED]> wrote:
> Why not use source control with eclipse, as it normally integrates 
> (with p4, cvs, and others), and then when ready to deploy, do a sync 
> of your repository on the server?
> 
> I've been doing this for a while (using Perforce as my SCM) and  not 
> only does it guarantee only sending checked-in code to your servers, 
> but it also allows you to shut off your ftp server.
> 
> I actually have a CF site which is set up to do a Sync/Update from my 
> source control, and I go there to pull new files.
> 
> -dov
> 


--
Barney Boisvert
[EMAIL PROTECTED]
360.319.6145
http://www.barneyb.com/

Got Gmail? I have 50 invites.







~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Logware (www.logware.us): a new and convenient web-based time tracking 
application. Start tracking and documenting hours spent on a project or with a 
client with Logware today. Try it for free with a 15 day trial account.
http://www.houseoffusion.com/banners/view.cfm?bannerid=67

Message: http://www.houseoffusion.com/lists.cfm/link=i:4:213499
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to