How to develop on the host?

Actually here's the thing - there is a project folder with 2 folders, one for development and another where everything is going, until this moment I did everything on the LAN with browsersync, that is, the entire development went to localhost:9000 and when you need to show the result to the customer need to open the FTP Manager and handles to upload the folder and then drag a link and show and this carousel while all changes do. And the second way is to SFTP galpa which allows you to merge the folder where all going to the server, but this too takes time and task you want to abort (of course you can throw in the default task galpa and constantly deplot hosting but a lot of time is a constant)

Actually a question: how to developerit directly on the hosting? what would for example to go to www.somesite.com and everyone in real time to observe how things are changing which saves us the trouble of FTP in General, we can only address hosting galpe to change to the new project. Whether really such to implement? And I want to ask the elders how you do it all, live with sftp?
July 12th 19 at 16:40
4 answers
July 12th 19 at 16:42
Solution
discover Docker

it is already possible
will look in that direction, but I think my problem is still the sand in a bucket to pour KAMAZ - Gerald.Prosacco73 commented on July 12th 19 at 16:45
July 12th 19 at 16:44
Solution
Autodeploy in phpStorm (in any other IDE, too, probably is) conveniently solves the problem, immediately pouring just the changed files via ftp.
in fact the same as in halpe, I thought someone knows some secret I do wrong - Gerald.Prosacco73 commented on July 12th 19 at 16:47
in halpe not tried ftp. but if every time he fills a whole directory, it is not the same. - Gerald.Prosacco73 commented on July 12th 19 at 16:50
: No, there everything can be configured though all folder Noda) just src: and though a specific file - libby.Zboncak commented on July 12th 19 at 16:53
July 12th 19 at 16:46
How to developerit directly on the hosting?

Bad idea, really. For development - use the environment as similar to prod.
To fill - then it all depends on the technology stack that you are limited. But as the variat - build the directory on the server with git, and then fill in the working directory using rsync. Through Docker. Through tar archives,...
But diploy and manual edit of code must be independent. Otherwise 99.99% at the most opportune time shoot yourself yaytsy.

what would for example to go to www.somesite.com and everyone in real time to observe how things are changing which saves us the trouble of FTP in General, we can only address hosting galpe to change to the new project.

I had not realised why? Make release -> all see the changes/

And I want to ask the elders how you do it all, live with sftp?

Development under Vagrant. All edits Committee in a common repository. In the hour H on the prod pull and rebuild.
To do this then that would show the customer rezalt no fill in the host, that is still what the client will look at localhost:9000 does not need to re-upload it there, but are understood - popabol, thank you

PS there customer your host only under my development, nobody sees it except me and him - Gerald.Prosacco73 commented on July 12th 19 at 16:49
And... well so you would have immediately said that "hosting" is a dev environment)) the Only change to this environment - Bild catalog === the working directory. - Gerald.Prosacco73 commented on July 12th 19 at 16:52
July 12th 19 at 16:48
Why such distortions? Browsersync is able to give external link that you can show the work to anyone.

gulp.task('browser-sync', function() {
 browserSync.init({ 
 tunnel: true
});
});

Find more questions by tags Gulp.jsWeb Development