How to deploy a fullstack project?

Question

Software Deployment

How to properly and conveniently organize software deployment and application of edits?

The problem is this:
1. I'm building the site according to the layout, it's going to webpack/gulp, something else. At the output, I have a build folder with the necessary files that are correctly displayed in the browser.
2. Suppose there is more functionality on vue.js / svelte, etc., for good, it also needs to be built somehow into this build from the first paragraph in order to see the whole picture and how it works in conjunction with the site. Here you have to copy this vue.js / svelte build by hand into the site build from point 1. Or write additional copying of this build into the build of point 1.
3. Then, the result of these efforts should be embedded, for example, in Laravel. Html files from build 1 are now called something there.blade.php, split into modules, components, and so on.
4. The functionality is written in PHP.
5. When everything is tested and working, it is uploaded to the combat server.

It seems to be everything, but then it turns out that it is necessary to make a change in the layout of the site. And here the hell begins . I make changes to point 1, I rebuild. I'm looking for this file in the blade laravel templates, the changes in which I need to shove. I get up before the question, replace everything and prescribe all sorts of {{ $variable }} with a new one or make changes in the finished blade template in pieces. Update css file in laravel.
Save and check. If everything is successful, I upload the changes to the combat server.

And it would be fine if there are 2-3 such edits, but when there are a lot of them, this chain must be done again and again by hand. If you make a mistake somewhere and copy something wrong or forget to update it, upload something wrong to the server, everything falls apart. It's just awful. Help, please, how to deal with all this?

Answer 1

Laravel has Laravel Mix as a bundle, which quietly allows you to optimize all your shenanigans.
Run the command npm run watchand calmly write the code, if you need to update the page with changes, connect browserify.
Look towards Laravel Envoy , set up all the data for deploying to the server. All this is deployed from the git repository of your project.
As a result, the entire route from making edits to deploying the project essentially consists of the following steps:
1. Perform edits, view through npm run watch
2. Commit everything to your repository.
3. Execute the command envoy run deployand all changes from the repository are pulled to the server.
That's all.

Answer 2

What kind of hell is not very clear. I also have vue blade laravel bootstrap. I use npm run watch commands - I make changes, npm run prod - production. Next git + forge for deployment. No problems/inconvenience at all.

Answer 3

Git was invented for this.