I think it’s a little strange. first, it is not like the way of modular design. Usually, each module should have there own configs. In this way, each module can be more easily maintained.
second, now we base on Spring, and the config has priority in Spring. When in developing mode we can set configs in each module, and when in deploying mode we should only use one merged config, it will overwrite the default value. [email protected] zhukai/nauu ygsoft > On Feb 16, 2020, at 9:00 PM, lidong dai <[email protected]> wrote: > > hi, > for now there are too many properties configuration file in src/resource > dir, we maybe forget the detail location of some properties file. usually > developer must go to the resource directory under each module to see if the > configuration in this directory, I think this situation needs to be > changed. > > I suggest that merging these already exists properties files (includes > alert.properties, application.properties, application-api.properties, > quartz.properties, common.properties) into one big properties file ? Do > you have any idea. > > By the way, I will delete the unnecessary configuration items to simplify > the configuration. The unnecessary configuration items will be placed in > the official website tuning document. > > > > > Best Regards > --------------- > DolphinScheduler(Incubator) PPMC > Lidong Dai 代立冬 > [email protected] > ---------------
