Are you working on your projects locally or remotely?

Question

Programming

I make websites locally and then upload them via FTP-manager to the server. On local I use Denwer. Recently, more and more began to experience inconvenience in working in this way, because. I have to work immediately on three computers: work, home and laptop. I have to store all projects on a mobile HDD, which I always carry with me and connect to the computer on which I will work.
Someone advised using clouds. Tried to work through dropbox and yandex.disk. Those. all projects together with Denver kept there. But in the end, the files constantly came into conflict, duplicates were created, they did not always have time to synchronize before the computer was turned off, etc. In short, there were inconveniences.
Recommended VPS. But then it turns out that when working with a project, you always need to first upload the file to the local area, work with it, and upload it back. Or use an editor that supports FTP in such a way that it works with the remote file system as with the local one. I am working in Sublime and phpStorm.
Can anyone give advice on how to properly organize the work in my case?

Answer 1

PHPStorm + GIT Deploy the
last one somewhere on the VPS and link the clients to the code, if necessary.

Answer 2

Look, Windows development is a pain. There is no normal console, and sooner or later it will be needed, the existing solutions are quite crutch. Throw this idea and go to the next level. I recommend switching to Linux as soon as possible, install ubuntu or mint as the second system at home (they are almost identical), it will come in handy for you. On it, you train in an elementary way to set up a LAMP or LEMP stack . If you are not friends with the console at all, then it will be hard, but with minimal skills you will figure it out quickly.
Next, create an account on bitbucket.com - you can store git repositories there for free, including private ones. playingwith git. Now your code can always be transferred to any machine, even in Denwer on a laptop, even in production, there would be Internet.
In principle, this is already enough for productive work, for further development, play around with vagrant - this is such a thing for virtualization. You can create a bunch of machines with a different set of software, for debugging at least a bald trait.
Then you can start a VPS for $5 per month. Get $10 using my referral link , enough for a couple of months of testing. I recommend to arrange something like hosting on it . It will be easy to administer, you can launch some of your projects, and immediately show the result to the client.

Answer 3

The life of a typical PHP programmer is hard and unsightly
. No mobile HDDs. No FTP sync.
Well, specifically on the issue:
Of course, locally. You have described so many problems, and it is you who are working on your own. Imagine that you will need to work together. Threesome. Ten of them. All scattered around the world and there is only skype.
Each developer should have their own comfortable unique environment.
0. Instead of Windows - * nix
1. Instead of Denver - a built-in web server to start with. Then, if necessary (with your approach, it may not appear soon), a full-fledged web server.
2. Instead of dropboxes and mobile HDDs - a version control system
3. Instead of FTP synchronization - some normal deployment workflow (for example, www.davegardner.me.uk/blog/2012/02/13/php-deployme... ). Plus something keeping track of dependencies (like https://getcomposer.org/ )

Answer 4

Vagrant + Ansible + Git or Docker + Git

Answer 5

... and in such a way that it works with the remote file system as with the local one.

sshfs

Answer 6

pycharm + git(bitbucket private) + database on VDS

Answer 7

I have a VPS specifically for small projects and for development (to immediately show clients). It is mounted via sshfs (under Linux or OS X), and the work is carried out as with a local server. Under Win sshfs, of course, no. The only alternative that somehow agreed to work is ExpanDrive.
Well, you need to have some kind of VCS, git or Mercurial is the same. So that we don’t do any improvements in production, and so that there are no problems when uploading updates.
In some cases, you can also raise a local server (for example, it is supposed to be developed in the absence of high-quality Internet). In the presence of VCS, this is then easily poured into any server, whether it is a test or working one.

Answer 8

Connecting to a project remotely via FTP or SSH, even with an IDE, is hell.
Even using Linux and mounting a folder is still hell.
Moreover - editing the code on the server directly is the main cause of hell, and not possible breaks when edits are not saved at all.
Only Git, only deploy commits and nothing else.
Development only on local, the system should be easily deployed with test data.