Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Ok noob question: I have a little micro AWS EC2 instance running, and I'm going through this Django tutorial. SSH'ing into my EC2 means that all the work I'm doing, like editing the config files, making Django apps/projects, etc. is very slow, with lag (my internet connection is not fast).

Could/should I be doing most of the work locally, then just uploading the files to the correct locations when I'm done, and then do all the apache configurations through the slow SSH only?

share|improve this question

closed as not constructive by Andrew M., EEAA, Khaled, Tom O'Connor, MDMarra May 15 '12 at 0:01

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

Working on the file locally:

  • Pros: You edit the file locally with zero lag.
  • Cons: You need to upload the file in order to test.

Working on the file remotely:

  • Pros: The file is immediately available for your app.
  • Cons: You have to deal with lag while editing.

Not quite sure what else there is--if the lag is bothering you, edit it locally and upload it (or consider using something like sshfs).

share|improve this answer
+1. Work locally, push back for testing. – Tom O'Connor May 13 '12 at 23:04

Not the answer you're looking for? Browse other questions tagged or ask your own question.