Currently the front and back ends are deployed separately, using nginx as a static resource parser. In the next version, to reduce dependencies, we will consider removing nginx and use jetty to implement.
Best Regards --------------- DolphinScheduler(Incubator) PPMC Lidong Dai 代立冬 [email protected] --------------- On December 1, 2019 at 21:34:01, Sheng Wu ([email protected]) wrote: Why do you require Nginx? Why Spring Zuul container, or Tomcat can’t work? Sheng Wu <[email protected]>于2019年12月1日 周日下午9:32写道： > OK. Then you have this dependency implicitly. > But if you are really doing this, you need to get through all dependency > of Nginx too. Because you force users to use Nginx now. > > I would suggest the whole DS community could take part in this discussion. > What is the best and quick solution for us. > > lidong dai <[email protected]>于2019年12月1日 周日下午9:28写道： > >> >> >> >> On December 1, 2019 at 21:02:21, Sheng Wu ([email protected]) >> wrote: >> >> >> >> lidong dai <[email protected]>于2019年12月1日 周日下午7:06写道： >> >>> Thanks for seriously check and review. >>> >>> Questions >>> 1. For your frontend dist tar, why do you require Nginx in your >>> `install-dolphinscheduler-ui.sh`? Does the frontend depend on Nginx? If >>> logically yes, Nginx is your dependency lib, and license should be >>> included. Look like `BSD-2` from >>> https://github.com/nginx/nginx/blob/master/docs/text/LICENSE. As you are >>> >>> Java based project, what do we need this? Spring boot should have >>> already a >>> good container for webapp. Could someone explain this? >>> >>> >>> As one more option, does nginx need to be written to the license file? >>> >> >> I just read your document of frontend deployment. Both ways(auto or >> manually), you are downloading Nginx. You said, this is one more option, >> but where are other options? How could user do if they don’t want Nginx, >> and whether it is working now? >> >> My point is, your release tar and your document make me feeling you need >> Nginx, rather than an option. If this is not wrong, I think you should >> describe it in your document. >> >> >> >> Thanks, for now we indeed need nginx, we will add nginx to ui-licenses >> directory. >> >> >> >>> >>> 2. Where is the documentation for this release? Does every release have >>> its >>> own doc? Or the documents are same for every release？ >>> >>> the document address：https:// >>> <https://dolphinscheduler.apache.org/en-us/docs/user_doc/quick-start.html> >>> dolphinscheduler.apache.org/en-us/docs/user_doc/quick-start.html ，every >>> document has its own doc >>> >>> >>> >>> Suggestion >>> 1. As you are using many Apache 2.0 licensed libs, if the license file is >>> >>> standard Apache 2.0 license, you could add a new catalog like this, and >>> no >>> LICENSE file required. >>> ======================================================================== >>> >>> Apache 2.0 licenses >>> ======================================================================== >>> >>> >>> The following components are provided under the Apache License. See >>> project >>> link for details. >>> The text of each license is the standard Apache 2.0 license. >>> >>> We will continue to remove third-party dependencies. Now the bloated >>> list display will always remind us to do it more firmly. In the near >>> future, we will remove a considerable part of the dependencies. >>> >>> >>> Best Regards >>> --------------- >>> DolphinScheduler(Incubator) PPMC >>> Lidong Dai 代立冬 >>> [email protected] >>> --------------- >>> >>> >>> -- >> Sheng Wu 吴晟 >> >> Apache SkyWalking >> Apache Incubator >> Apache ShardingSphere, ECharts, DolphinScheduler podlings >> Zipkin >> Twitter, wusheng1108 >> >> -- > Sheng Wu 吴晟 > > Apache SkyWalking > Apache Incubator > Apache ShardingSphere, ECharts, DolphinScheduler podlings > Zipkin > Twitter, wusheng1108 > -- Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
