How to avoid mishandling test and production environments

Hello.

Regarding the issue of confusing production and test environments, one answer is to clarify the release flow.In my previous PHP project, I used git for easy release management.

The administrator is responsible for production applications, and all other tasks are done in a test environment or staging environment, so there is no inadvertent mix-up.Automation has also been a hot topic in recent years.

For example, if you prepare a staging environment (=same as production) between the test environment and the administrator makes a simple copy after careful testing from staging to production, it will be easier to prevent "out of the blue" (basically no workers touch it).

I think the operating environment and resources are different, so it may not be the answer you wanted, but I would appreciate it if you could consider it as one of your know-how.