Fully remote development on pycharm with virtualenv

Question

Django

There is a server with several django projects, each of which is in its own virtualenv.
How to open, develop and debug these projects through pycharm?

Is it necessary to mount remote directories via sshfs to do this?
Is it possible to do this without a local python interpreter at all, for example on a windows machine?

UPDATE:
JetBrains support replied that the virtualenv environment will work correctly if added as a Remote Interpreter
(e.g. /var/www/project/var/.env/bin/python)
and that you can work with a remote repository by first downloading its local copy, which then needs to be sent through the "Deployment feature".

Answer 1

I strongly advise you to start by introducing git or svn into these projects.
This will save you from a lot of fails in the future, add discipline, even if you work alone.
The ability to roll back to a specific version (a bugged feature, we just roll back to the previous version and everything does not need to be restored in memory where what and when was corrected), knowledge of what things were actually done and when (alas, the memory is not perfect), provided that the commits are correctly described and filled out, it is very important.
Structuring code by commits.
Feel free to give descriptions to commits, you do it for yourself.
Deployment to a new environment with a couple of commands.
On the subject, of course, you need to have a separate virtualenv for each of the projects.
Fortunately, in pycharm this is done in the Interpreter menu (http://www.jetbrains.com/pycharm/quickstart/configuring_interpreter.html) in two clicks. Installing packages is also in two clicks.
There may be problems with packages available only under Linux, but in this case a virtual machine or Dual Boot can save.

Answer 2

I have a small development vds, which I essentially use as a local machine, I only run runserver from it, so I don’t need to monitor it myself, then commits are made and everything is uploaded to the working server.
So there are fewer problems, this vds is only for development, nothing will accidentally break there, the server has one fixed ip if suddenly there are bindings somewhere, it works faster. located in a location with a good canal.