How do you avoid misusing test and production environments?
I think most people are doing the following pattern.
Three ingenuity to avoid mistaking the test site for the production site
Chrome extension to avoid misreading test and production environments - Qiita
However, httpd.conf may not work (quite often)
Don't forget to let everyone set it up because it can cause leaks.
I would like to set it up on the site side and on the server side.
Thank you for your advice.php server-management
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.
371 Update Flask User Information
366 To Limit Column Values to Strings in a String List Using sqlalchemy
339 Understanding the Meaning of mpm prefork Settings
356 I want to create an array of sequences from "1" to a specified number.
339 Scrap text information after the "View More" button when searching in the Yahoo! News search window
© 2023 OneMinuteCode. All rights reserved.