Answer the question
In order to leave comments, you need to log in
What is the method of working with Git if the error is only in production?
Site on Laravel. Upload to Git. Then deploy via forge.
However, there is an error. And only in production (on the local everything is ok). And it turns out that in the process of testing options, you need to upload to git and deploy the project every time. How do you work in this situation? When the error is visible only in production. Also in git and deploy after each sneeze?
Answer the question
In order to leave comments, you need to log in
I have another host next to the production, sharpened on the same resources and the same git branch as the production. but open only to me. I first open it and see that everything is ok.
Get rid of the "checkout to git" form, you should work with git all the time, not checkout to it. The assembly for testing should be the same as for production, otherwise such errors will haunt you all the time. Automate the assembly, and there will be no questions "deploy after each sneeze?".
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question