For those that want better SFTP support in ST2, I urge you to look at WinSCP. In its preferences, you can specify an editor. Now, when you double click a file, it opens in that editor - you make changes and hit CTRL-S to save the file. WinSCP monitors that file (stored in a local temp buffer) and automatically uploads it back to the server for you.

You don't get to utilize the sidebar of ST2 as it's intended. But you do get all the features of WinSCP. For the few sites I still live-edit, this is the best method I've found. All the power of ST2 far outweighs the SFTP plugin that N++ (or any other editor) has.

SeanWcom wrote:For those that want better SFTP support in ST2, I urge you to look at WinSCP. In its preferences, you can specify an editor. Now, when you double click a file, it opens in that editor - you make changes and hit CTRL-S to save the file. WinSCP monitors that file (stored in a local temp buffer) and automatically uploads it back to the server for you.

You don't get to utilize the sidebar of ST2 as it's intended. But you do get all the features of WinSCP. For the few sites I still live-edit, this is the best method I've found. All the power of ST2 far outweighs the SFTP plugin that N++ (or any other editor) has.

I have a good reason for FTP to be built in.And yes, I know what git is and use it for most of my projects.But sometimes you need to edit files on remote ftp that are NOT website related.E.g. wowza config files or some internal settings for a script, which is running on remote server.When you have a dozen of servers and just a few configs on each of them I find it more complicated to bring in the git for such simple tasks.

I would love Sublime Text to have built in FTP -- in the same manner as Coda.

--

I'm in support of the old-fashioned way of live editing sites.

I've made over 200 websites and know exactly what I'm doing. I work on multiple computers and have no desire to setup each with a development environment. I have no desire to pull from git repositories every time I want to make edits and then push them back. I'm working by myself on sites -- not with a team.

GIT is for version control and is FANTASTIC when you are writing software. It's FANTASTIC if you're working on a team project -- perhaps even a web app.

But creating a Wordpress or Drupal site on git? Having multiple machines with test environments installed? Having to setup repos for 100s of sites and push and pull whenever you want to make and test small changes? No thanks.

With database driven sites, often times I am working within the CMS aspect and the HTML/PHP template simultaneously and jumping back and forth.

When this is the case, using GIT is just cumbersome.

Besides, I also like to know how FAST things load remotely while I'm working on them. I don't care how fast they work on my local machine.

There's every advantage in the world to work on the actual thing.

The argument is "What if you mess something up?"

Answer: Fix it. Any argument that one could lose two weeks of work by editing this way is absurd. Who is so terrible at programming websites that they make one mistake and destroy that much code? I can understand destroying a database by mistake - but Git has nothing to do with that. And if you wrote code that produced a horrible SQL query that destroyed a database, I'm not sure what git would do to help.

--

I'm not working on enterprise level projects -- and if I was, I'm sure I'd have a team with me and we'd be working on the local intranet on a dev site and pushing things at a different rate and discussing iterations over coffee.

But is that who Sublime is developed for?

And are the people who wrote Coda absolutely idiots?

No, of course they aren't idiots. They wrote an amazing FTP client and made an editor that has it built in to facilitate this function. The product sells like hotcakes and there are many people out there using it this way without catastrophes caused by idiotic programming.

--I do most of my development on a Windows 7 desktop -- I find Windows to be much easier to work with than MacOS for many reasons. I use a MacBook Pro when I'm working remotely. I yep, I use Coda 2 on my MacBook and it's absolutely awesome. I absolutely would LOVE to have it on my PC. Coda would be my #1 reason to get an iMac as my next computer. If not the only reason.

I recommend using something like Swish on Windows. I'm pretty sure OSX supports this sort of thing natively. Mount the remote filesystem as a folder/drive and your editor doesn't have to be a network client as well.

I'm new to ST2 and after using it for a day, I must say it's unlike any editor I've used, reminds me of the seamless workflow of Maya Autodesk. I'm a bit of an old school Adobe enthusiasts and have been using the code view in Dreamweaver for years . Although most of the features DW presents to programmers are useless to say the least, one thing I do miss is the built in FTP client that maintains the folder structure of project you create, it's clean and concise. After being so used to DW, I couldn't stand having to switch to a desktop FTP client every time I needed to upload something, I like everything in one spot. So after a bit of Googling, I found an SFTP plugin that does the one thing I need it to do, it maintains the folder structure allowing file transfer with the click of a button, I immediately purchased a license after using the plugin for literally 10min, I'd highly recommend it to anyone looking for native SFTP/FTP support : http://wbond.net/sublime_packages/sftp .

If you are someone who has many clients/projects rolling at once, working locally can be extremely tedious, especially with multiple database driven CMS, who wants to maintain 10-15 different databases locally? I even find while working on an app, syncing with a remote server can be beneficial for unit testing and whatnot. I can honestly say Sublime SFTP is an excellent replacement for a desktop client if you don't mind shelling out the $16 bucks for a license, well worth it IMO.

Answer: Fix it. Any argument that one could lose two weeks of work by editing this way is absurd. Who is so terrible at programming websites that they make one mistake and destroy that much code? I can understand destroying a database by mistake - but Git has nothing to do with that. And if you wrote code that produced a horrible SQL query that destroyed a database, I'm not sure what git would do to help.

It happened couple of times to do major changes to a file, just to be asked by my clients to revert it back after few days/a week.

It happened several times to change a file and my client to overwrite just because his editor remembered last opened file and just overwrite.

It happened once that the editor - e-texteditor - to crash just while the file was saved/transfered. After i restarted the editor i was shocked to find a beautiful empty file (i found out eventually that had a temp file; it was the worse 10 minutes of my developer life!)

Just because you have over 200 websites made and know exactly what are you doing doesn't protect you from a major screw up. And when you do - because you gonna screw up eventually, it's just a matter of time! - won't be nice.

I'm interested too in a built-in FTP/SFTP support in sublimetext.I'm seeing that the discussion is moved on "if is this right or not?". Personally i agree that it's unsafe for many reasons... but in the real world there are a lot of situation who requires remote editing. Not just a matter of development, sometime just need to change configurations files remotely throught ftp or ssh or work on embedded platform that have just an ftp or telnet access. I think we are all grow up people, we know the risks and we accept them. So, if it's possible come back to the original topic, there's any way to have a real working ftp/sftp on sublime text 3? Until now i'm using it with filezilla (who support remote editing) but everytime i change a file i need to put the focus on the filezilla window and accept the new file update. A fully integrated support in sublimetext would be really really more reliable

Answer: Fix it. Any argument that one could lose two weeks of work by editing this way is absurd. Who is so terrible at programming websites that they make one mistake and destroy that much code? I can understand destroying a database by mistake - but Git has nothing to do with that. And if you wrote code that produced a horrible SQL query that destroyed a database, I'm not sure what git would do to help.

It happened couple of times to do major changes to a file, just to be asked by my clients to revert it back after few days/a week.

It happened several times to change a file and my client to overwrite just because his editor remembered last opened file and just overwrite.

It happened once that the editor - e-texteditor - to crash just while the file was saved/transfered. After i restarted the editor i was shocked to find a beautiful empty file (i found out eventually that had a temp file; it was the worse 10 minutes of my developer life!)

Just because you have over 200 websites made and know exactly what are you doing doesn't protect you from a major screw up. And when you do - because you gonna screw up eventually, it's just a matter of time! - won't be nice.

So you are saying if you're working directly on FTP you're doing it wrong, then go on to give several examples of problems you ran into because you don't have a proper backup system set up.

Every issue you had would easily be fixed with a proper backup system. Having no backup system is a much more egregious example of 'doing it wrong' than directly editing files via FTP (IMO).