Front-end development, correct build?

Question

css

Well, everything is clear here - the project was opened, and it was pulled into production.
What next? If there are edits already on the planted layout, where do we edit? At home again or directly on the server, then the assembly can already be thrown away?

Answer 1

If a company values ​​the quality of the product and the security of its customers' data, then the assembly and rollout of the new version is carried out automatically by the Continuous Intrgration server. Programmers just do not have access to the product. Only the CI server has access to the product. The programmer has access only to the GIT repository of the project. All work is carried out in its own environment and in a separate branch. The branch is then tested on a test environment (close to production), corrected if necessary, and then merged into the main branch of the project. After that, CI picks up the changes, builds the front and back, and rolls it out for production. This is a very general option. There's a bunch of nuances in there.
Personally, I prefer to follow the path described above from the first day of work, even when I work alone. Because in this case, you can always roll back to the latest stable release, leave as a lady and finish everything the next day. Instead of fixing something with bulging eyes and trembling lips all night (which is a sign of a very low-quality project).
UPD
I forgot to say that this path is not easy. You need to practice for about half a year. But on the other hand, you get quiet nights and a healthy complexion for life, so it's worth it.

Answer 2

editing the code immediately on the server - what can go wrong, right?)
First, all edits are made locally, then deployed.

Answer 3

what if I want to fix something right on the server

Who says so, or a professional of the highest class, and perfectly understands what it threatens, how then to transfer these edits to the repository, when it is really necessary / cheaper to do it, how to insure against the problems that such edits cause, and, in theory, should be ready to take responsibility for the consequences. Those. in this case, you don't have to worry about it at all.
Or vice versa - not a professional at all. What do you do in this case in such a team is a philosophical question.

Answer 4

At home, then we collect and fill. It is convenient to do this with git