You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For most web projects, the final entry for users is a URL. Always, different URL means different environment, also different server or server config. Therefore, the ways we can use to bind environments are clear.
Bind environment with URL.
Bind environment with server or server config.
Bind environment with project config.
So, which one is the best? Well, it depends.
Bind Env By URL
Bind Env By Server
Bind Env By Project Config
It's common to see many build commands in package.json like npm run build:test, npm run build:sit, npm run build:prod. The point is building different bundles for different environments.
The text was updated successfully, but these errors were encountered:
xianshenglu
changed the title
Several Ways of Web Project Environment Binding
Several Ways of API_ORIGIN in Web FrontEnd Project
Aug 13, 2023
For most web projects, the final entry for users is a URL. Always, different URL means different environment, also different server or server config. Therefore, the ways we can use to bind environments are clear.
So, which one is the best? Well, it depends.
Bind Env By URL
Bind Env By Server
Bind Env By Project Config
It's common to see many build commands in package.json like
npm run build:test
,npm run build:sit
,npm run build:prod
. The point is building different bundles for different environments.The text was updated successfully, but these errors were encountered: