We're all well aware of Coda's shortcomings when it comes to
publishing. If changes are made outside the site, Coda simply ignores
those files as being new. Fair enough, I've gotten used to manually
marking files for publishing as I change them and I've gotten used to
getting yelled at when I miss something. The problem now is that I'm
developing a static site that continuously has a development server
and a live server. Essentially I'm fed changes each week in advance, I
post them to the development server, they get approved by the client
and then I post them live.
My workflow here has two sites within Coda sharing one folder.
Everything is just fine on the development site. I make changes,
manually mark files where necessary and publish. However when it's
time to go live with these changes, the live site has no record of
anything being changed at all (assuming because the files were added
or marked outside of the active site). Therefore I've got to manually
follow through with a list of changes marking things one at a time or
I have to upload entire directories at once. For what it's worth,
Transmit doesn't help much as its synchronization isn't always
accurate.
Does anyone have a workaround for this? Perhaps I'm using the wrong
sort of workflow here? Traditionally I only use a development site
during the initial construction of a site so the live site gets dumped
in full and synchronization is never an issue.
> We're all well aware of Coda's shortcomings when it comes to
> publishing. If changes are made outside the site, Coda simply ignores
> those files as being new. Fair enough, I've gotten used to manually
> marking files for publishing as I change them and I've gotten used to
> getting yelled at when I miss something. The problem now is that I'm
> developing a static site that continuously has a development server
> and a live server. Essentially I'm fed changes each week in advance, I
> post them to the development server, they get approved by the client
> and then I post them live.
> My workflow here has two sites within Coda sharing one folder.
> Everything is just fine on the development site. I make changes,
> manually mark files where necessary and publish. However when it's
> time to go live with these changes, the live site has no record of
> anything being changed at all (assuming because the files were added
> or marked outside of the active site). Therefore I've got to manually
> follow through with a list of changes marking things one at a time or
> I have to upload entire directories at once. For what it's worth,
> Transmit doesn't help much as its synchronization isn't always
> accurate.
> Does anyone have a workaround for this? Perhaps I'm using the wrong
> sort of workflow here? Traditionally I only use a development site
> during the initial construction of a site so the live site gets dumped
> in full and synchronization is never an issue.
I do have an SVN repository though we're just using that for
collaboration. Additionally neither the development server nor the
live server support svn directly. Keep in mind though that I am new to
svn (only been using it for 4-5 months now) so I may be overlooking
something here.
Joe
On Jul 8, 2009, at 11:43 AM, Alexander Faust wrote:
> I think you should consider installing an SVN repository. That's a
> great way of keeping two Sites synced even on different machines.
> Von meinem iPhone gesendet
> Am 08.07.2009 um 17:18 schrieb Joey Angrisano <j...@digisquid.com>:
>> We're all well aware of Coda's shortcomings when it comes to
>> publishing. If changes are made outside the site, Coda simply ignores
>> those files as being new. Fair enough, I've gotten used to manually
>> marking files for publishing as I change them and I've gotten used to
>> getting yelled at when I miss something. The problem now is that I'm
>> developing a static site that continuously has a development server
>> and a live server. Essentially I'm fed changes each week in
>> advance, I
>> post them to the development server, they get approved by the client
>> and then I post them live.
>> My workflow here has two sites within Coda sharing one folder.
>> Everything is just fine on the development site. I make changes,
>> manually mark files where necessary and publish. However when it's
>> time to go live with these changes, the live site has no record of
>> anything being changed at all (assuming because the files were added
>> or marked outside of the active site). Therefore I've got to manually
>> follow through with a list of changes marking things one at a time or
>> I have to upload entire directories at once. For what it's worth,
>> Transmit doesn't help much as its synchronization isn't always
>> accurate.
>> Does anyone have a workaround for this? Perhaps I'm using the wrong
>> sort of workflow here? Traditionally I only use a development site
>> during the initial construction of a site so the live site gets
>> dumped
>> in full and synchronization is never an issue.
You can use different Folders for your Development and live Sites.
Then Sync them via svn. When syncing with svn all changed Files should
be marked for Publishing then :)
Von meinem iPhone gesendet
Am 08.07.2009 um 18:03 schrieb Joe Angrisano <j...@digisquid.com>:
> I do have an SVN repository though we're just using that for
> collaboration. Additionally neither the development server nor the
> live server support svn directly. Keep in mind though that I am new to
> svn (only been using it for 4-5 months now) so I may be overlooking
> something here.
> Joe
> On Jul 8, 2009, at 11:43 AM, Alexander Faust wrote:
>> I think you should consider installing an SVN repository. That's a
>> great way of keeping two Sites synced even on different machines.
>> Von meinem iPhone gesendet
>> Am 08.07.2009 um 17:18 schrieb Joey Angrisano <j...@digisquid.com>:
>>> We're all well aware of Coda's shortcomings when it comes to
>>> publishing. If changes are made outside the site, Coda simply
>>> ignores
>>> those files as being new. Fair enough, I've gotten used to manually
>>> marking files for publishing as I change them and I've gotten used
>>> to
>>> getting yelled at when I miss something. The problem now is that I'm
>>> developing a static site that continuously has a development server
>>> and a live server. Essentially I'm fed changes each week in
>>> advance, I
>>> post them to the development server, they get approved by the client
>>> and then I post them live.
>>> My workflow here has two sites within Coda sharing one folder.
>>> Everything is just fine on the development site. I make changes,
>>> manually mark files where necessary and publish. However when it's
>>> time to go live with these changes, the live site has no record of
>>> anything being changed at all (assuming because the files were added
>>> or marked outside of the active site). Therefore I've got to
>>> manually
>>> follow through with a list of changes marking things one at a time
>>> or
>>> I have to upload entire directories at once. For what it's worth,
>>> Transmit doesn't help much as its synchronization isn't always
>>> accurate.
>>> Does anyone have a workaround for this? Perhaps I'm using the wrong
>>> sort of workflow here? Traditionally I only use a development site
>>> during the initial construction of a site so the live site gets
>>> dumped
>>> in full and synchronization is never an issue.
OK so no SVN on the server - how about rsync and ssh?
I tried and failed and gave up getting Git to push changes to my
server [ n00b ]. So dusted off a couple of old rsync scripts I used to
use back in the days of RsyncX. That was before rsync was made a
native MacOSX binary with HFS+ support (not needed now I'm out of
DTP!) or became the foundation of Time Machine...
Rsync is fabulous - it can do a sync based on checksums of the files'
content. Modification dates etc be damned. That and more magic. Have
alook into for yourself. Maybe there's other folk out here who can
confirm or deny this. (and any of the following too... !)
If you have ssh access and rsync on both servers (type "rsync --
version" in a terminal window to see) you could try something along
the lines of:
time - to tell you how long it takes
-a for archive mode (overwrites any changes on the destination)
-c skip based on checksum, not mod-time & size (killer feature)
-z compress file data during the transfer
-e specify the remote shell to use (in this case ssh)
--delete will delete file not in the source folder
--progress gives feedback on how things are going
--exclude specifies what to ignore (in this case anything in any
folder ending in ".git")
--dry-run doesn't actually change any files - just goes through the
motions so you're happy all is well
When you're happy - lose the "--dry run" and go!
On Jul 8, 6:23 pm, Alexander Faust <bard...@gmail.com> wrote:
> You can use different Folders for your Development and live Sites.
> Then Sync them via svn. When syncing with svn all changed Files should
> be marked for Publishing then :)
> Von meinem iPhone gesendet
> Am 08.07.2009 um 18:03 schrieb Joe Angrisano <j...@digisquid.com>:
> > I do have an SVN repository though we're just using that for
> > collaboration. Additionally neither the development server nor the
> > live server support svn directly. Keep in mind though that I am new to
> > svn (only been using it for 4-5 months now) so I may be overlooking
> > something here.
> > Joe
> > On Jul 8, 2009, at 11:43 AM, Alexander Faust wrote:
> >> I think you should consider installing an SVN repository. That's a
> >> great way of keeping two Sites synced even on different machines.
> >> Von meinem iPhone gesendet
> >> Am 08.07.2009 um 17:18 schrieb Joey Angrisano <j...@digisquid.com>:
> >>> We're all well aware of Coda's shortcomings when it comes to
> >>> publishing. If changes are made outside the site, Coda simply
> >>> ignores
> >>> those files as being new. Fair enough, I've gotten used to manually
> >>> marking files for publishing as I change them and I've gotten used
> >>> to
> >>> getting yelled at when I miss something. The problem now is that I'm
> >>> developing a static site that continuously has a development server
> >>> and a live server. Essentially I'm fed changes each week in
> >>> advance, I
> >>> post them to the development server, they get approved by the client
> >>> and then I post them live.
> >>> My workflow here has two sites within Coda sharing one folder.
> >>> Everything is just fine on the development site. I make changes,
> >>> manually mark files where necessary and publish. However when it's
> >>> time to go live with these changes, the live site has no record of
> >>> anything being changed at all (assuming because the files were added
> >>> or marked outside of the active site). Therefore I've got to
> >>> manually
> >>> follow through with a list of changes marking things one at a time
> >>> or
> >>> I have to upload entire directories at once. For what it's worth,
> >>> Transmit doesn't help much as its synchronization isn't always
> >>> accurate.
> >>> Does anyone have a workaround for this? Perhaps I'm using the wrong
> >>> sort of workflow here? Traditionally I only use a development site
> >>> during the initial construction of a site so the live site gets
> >>> dumped
> >>> in full and synchronization is never an issue.
Sadly I rarely have SSH access to any of my hosting accounts. It's all
low tech stuff really and so most clients opt for $5 month shared
accounts. I can SSH to my own server of course, but I'm not sure it's
worth the effort since that's the development server anyway. Oh well.
I was just hoping there was a simple, sane way for Coda to synchronize
a website other than manually clicking which files (can't even do
folders, ugh) to publish.
> OK so no SVN on the server - how about rsync and ssh?
> I tried and failed and gave up getting Git to push changes to my
> server [ n00b ]. So dusted off a couple of old rsync scripts I used to
> use back in the days of RsyncX. That was before rsync was made a
> native MacOSX binary with HFS+ support (not needed now I'm out of
> DTP!) or became the foundation of Time Machine...
> Rsync is fabulous - it can do a sync based on checksums of the files'
> content. Modification dates etc be damned. That and more magic. Have
> alook into for yourself. Maybe there's other folk out here who can
> confirm or deny this. (and any of the following too... !)
> If you have ssh access and rsync on both servers (type "rsync --
> version" in a terminal window to see) you could try something along
> the lines of:
> time - to tell you how long it takes
> -a for archive mode (overwrites any changes on the destination)
> -c skip based on checksum, not mod-time & size (killer feature)
> -z compress file data during the transfer
> -e specify the remote shell to use (in this case ssh)
> --delete will delete file not in the source folder
> --progress gives feedback on how things are going
> --exclude specifies what to ignore (in this case anything in any
> folder ending in ".git")
> --dry-run doesn't actually change any files - just goes through the
> motions so you're happy all is well
> When you're happy - lose the "--dry run" and go!
> On Jul 8, 6:23 pm, Alexander Faust <bard...@gmail.com> wrote:
>> You can use different Folders for your Development and live Sites.
>> Then Sync them via svn. When syncing with svn all changed Files
>> should
>> be marked for Publishing then :)
>> Von meinem iPhone gesendet
>> Am 08.07.2009 um 18:03 schrieb Joe Angrisano <j...@digisquid.com>:
>>> I do have an SVN repository though we're just using that for
>>> collaboration. Additionally neither the development server nor the
>>> live server support svn directly. Keep in mind though that I am
>>> new to
>>> svn (only been using it for 4-5 months now) so I may be overlooking
>>> something here.
>>> Joe
>>> On Jul 8, 2009, at 11:43 AM, Alexander Faust wrote:
>>>> I think you should consider installing an SVN repository. That's a
>>>> great way of keeping two Sites synced even on different machines.
>>>> Von meinem iPhone gesendet
>>>> Am 08.07.2009 um 17:18 schrieb Joey Angrisano <j...@digisquid.com>:
>>>>> We're all well aware of Coda's shortcomings when it comes to
>>>>> publishing. If changes are made outside the site, Coda simply
>>>>> ignores
>>>>> those files as being new. Fair enough, I've gotten used to
>>>>> manually
>>>>> marking files for publishing as I change them and I've gotten used
>>>>> to
>>>>> getting yelled at when I miss something. The problem now is that
>>>>> I'm
>>>>> developing a static site that continuously has a development
>>>>> server
>>>>> and a live server. Essentially I'm fed changes each week in
>>>>> advance, I
>>>>> post them to the development server, they get approved by the
>>>>> client
>>>>> and then I post them live.
>>>>> My workflow here has two sites within Coda sharing one folder.
>>>>> Everything is just fine on the development site. I make changes,
>>>>> manually mark files where necessary and publish. However when it's
>>>>> time to go live with these changes, the live site has no record of
>>>>> anything being changed at all (assuming because the files were
>>>>> added
>>>>> or marked outside of the active site). Therefore I've got to
>>>>> manually
>>>>> follow through with a list of changes marking things one at a time
>>>>> or
>>>>> I have to upload entire directories at once. For what it's worth,
>>>>> Transmit doesn't help much as its synchronization isn't always
>>>>> accurate.
>>>>> Does anyone have a workaround for this? Perhaps I'm using the
>>>>> wrong
>>>>> sort of workflow here? Traditionally I only use a development site
>>>>> during the initial construction of a site so the live site gets
>>>>> dumped
>>>>> in full and synchronization is never an issue.
