github-actions[bot] commented on issue #10999:
URL: 
https://github.com/apache/dolphinscheduler/issues/10999#issuecomment-1185429709

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar feature requirement.
   
   
   ### Description
   
   hi ,how can i build dolphinscheduler-ui select prod env use public path.
   ````js
   // v2.0.5 ,yarn run build:release,the route includes 
'/dolphinscheduler/ui',but yarn build prod not.
   "build": "npm run clean && cross-env NODE_ENV=production webpack --config 
./build/webpack.config.prod.js",
   "dev": "cross-env NODE_ENV=development webpack-dev-server --config 
./build/webpack.config.dev.js",
   "build:release": "npm run clean && cross-env NODE_ENV=production 
PUBLIC_PATH=/dolphinscheduler/ui webpack --config 
./build/webpack.config.release.js",
   ````
   Hello, I want to bring /dolphinscheduler/ui to the route after yarn build 
prod in version 2.0.5. If I add PUBLIC_PATH=/dolphinscheduler/ui to the build 
or dev script, the production will not be able to access the background. The 
development environment will not be able to debug, that is, the code under 
dolphinscheduler/dolphinscheduler-ui/src/js/conf/ will not respond. Do you have 
front-end documentation to use?
   
   
   ### Documentation Links
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to