ActiveState Community Site - "Save Remotely As" vs "Upload" - Comments

anything in Komodo 5

loubabe — Wed, 05 Nov 2008 15:40:57 -0800

This seems like a critical feature, at least for those of us who need to deploy our local files via FTP. Opening up a separate FTP client, finding the right file, etc. is extremely cumbersome.

sorry comment deleted

Joker — Wed, 22 Oct 2008 08:42:19 -0700

sorry
comment deleted

Great news!

grubolsch — Tue, 22 Apr 2008 13:49:39 -0700

Whould be great to see that implemented!

Re: remote sync/upload

ToddW — Wed, 02 Jan 2008 12:29:05 -0800

Just to let you know that we are looking into adding this feature to Komodo, though I cannot yet give an estimated arrival date.

The remote file API's are there for the impatient, if someone wishes to make an extension to support this, you can take a look at the remote drive tree extension for ideas:
http://community.activestate.com/komodo-extension/remote-drive-tree

Cheers,
Todd

Another vote for "upload"

wrightee — Wed, 02 Jan 2008 08:00:11 -0800

I'm used to using NuSphere which allows associating a server / upload path with a project for remote publishing. Being able to either right click on a file and select upload or Ctrl+Shift+S to save remotely is one of the best things I've found in an IDE for working speed.

I normally use a SVN repos for collab and a test server or two, exporting directly from the repository to the live installation and ftp uploading to the test server only, so rsync won't work for us.

Consider RSync

shanec — Mon, 09 Jul 2007 11:41:38 -0700

You might want to look into using rsync, there is an article about it here: http://community.activestate.com/faq/using-rsync-with-projects

"Save Remotely As" vs "Upload"

wolfe — Mon, 09 Jul 2007 11:16:20 -0700

I've been trying out Komodo for a few days and one thing keeps bugging me. The only way that I've found to transfer my work to the server is to use the "Save Remotely As..." function. Then as I continue to work, Komodo is making changes to the remote copy of the file without updating the local copy. When I close out Komodo and return to the local file later it is out of date.

What I'd like to see is a way to continue saving all work-in-progress changes to the local file and then allow me to upload the file as I need to. Am I missing something in Komodo that will allow me to do this?

I'm in a single developer environment and don't see the need to complicate things by going to CVS. And I'm not sure that would change anything about this issue anyway.