I love pycharm and they have been improving it. It has become my primary Django IDE and they give free licenses to qualifying open source projects. Of course FileZilla is good for FTP and cygwin has SSH and SCP. I use VirtualBox for instances and sometimes have to edit files locally on the machine with nano vim or emacs.
Good Coding, Matteius On Feb 8, 9:44 pm, broz <theb...@gmail.com> wrote: > I've been curious about workflow with Django sites (or other > frameworks for that matter). I LOVE being able to remote edit. I can > see where this request is coming from. If I want to edit a file on the > server, I just open it up on my local machine, edit, and save. The > SFTP transfer all happens behind the scenes. This is very efficient. > There are no risks. I am editing a test instance. I do use version > control, but that's not what this is about. > > In order to work on my code locally, I need to have a system set up > locally that mimics the remote system. So, I need to have a running > database, and a web server, and some other pieces and parts. My local > instance will not match the remote instance, ever. The remote uses > virtual hosts, the local one does not. The remote is an older version > of apache. The remote uses Oracle. Perhaps I could set my local system > up with old apache, and old Oracle. The remote server is remote, so > there's performance issues to consider. > > I can set something up locally, fiddle, fuss, make it work, and then > ship the changes to the server. Whoa, it doesn't work on the server, > because my local system is just not the same. > > This is why I want to remote edit my files. I want to test on a test > instance on the same server that will run the production version when > I'm done. And that's what I do with BBEdit. > > BBEdit does remote editing very very well. It's not an IDE. > > With BBEdit, I open the file, edit, test, edit, test. > > PyCharm is a great IDE, but it doesn't remote edit. I download, I open > the file, I edit, save, upload, test, edit, save, upload, test, edit, > save, upload, test. Pydev works this way too. Wingware, I donno. > Komodo? I donno. > > I would welcome enthusiastically, some recommendations on workflow, > given the constraints of the IDEs we have. There are lots of people > out there smarter than me. > > Thanks for bringing up this topic! > > Broz > > On Feb 8, 8:32 pm, Łukasz Rekucki <lreku...@gmail.com> wrote: > > > > > On 9 February 2011 02:03, Karen McNeil <karenlmcn...@gmail.com> wrote: > > > > So... that's a no, then? > > > > I mean, about the question I asked. You know, the "is there an IDE + > > > FTP program" question? > > > Quotinghttp://www.aptana.org/products/studio2: > > > File Transfer & Synchronization > > Support for one-shot as well as keep-synchronized setups. Multiple > > protocols including FTP, SFTP and FTPS. Ability to automatically > > publish your application to selected ISPs and hosting services. > > > > - I *do* do a very simple kind of version control, where I save a > > > numbered copy of the major site files > > > whenever I've made changes and I've got a stable, working site. > > > I've looked into Subversion and Git and, > > > believe me, they would be way overkill for my little projects. > > > Version control is never an overkill, if the setup is so simple (like > > in Git or Mercurial - that git init doesn't really cost you anything). > > Plus it solves 3 major problems: > > > 1) Keeping history for your own sanity. Too many times I seen people > > go crazy over code that "suddenly stoped working even if I revert the > > change". > > > 2) Backups - pushing your code to remote sites like Bitbucket or > > Github is a great way, to make sure you don't lose or your work. > > > 3) Deployment - Instead of uploading stuff via FTP, you can just push > > your changes to the site. This wil proably require some more knowledge > > about VCS, but it will save lots of time. > > > -- > > Łukasz Rekucki -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
