"/etc/default/<package-name>" should be shell script setting envars

[dhardy92]

Current format is java option only append to java command line.
This is not standards and not very flexible and expendable.
Shell let us include other source and split config in several files and responsibilities using source
Moreover, envars usage is a 12-factors app recommendation.

[kardapoltsev]

From Debian Policy Manual

Often there are some variables in the init.d scripts whose values control the behavior of the scripts, and which a system administrator is likely to want to change. As the scripts themselves are frequently conffiles, modifying them requires that the administrator merge in their changes each time the package is upgraded and the conffile changes. To ease the burden on the system administrator, such configurable values should not be placed directly in the script. Instead, they should be placed in a file in /etc/default, which typically will have the same base name as the init.d script. This extra file should be sourced by the script when the script runs. It must contain only variable settings and comments in SUSv3 sh format. It may either be a conffile or a configuration file maintained by the package maintainer scripts.

[kardapoltsev]

Hmm.. Seems that during refactoring we missed this. We should source /etc/default/app_name in init script.

[kardapoltsev]

@dhardy92, PR is welcome!

[knshiro]

Hello everyone, why was this reverted?
I had to modify my build.sbt to add lines to the bash script to be able to use environment variables and was happy to see that was put in the plugin...

[kardapoltsev]

See #491

[jasonmartens]

This bug should be re-opened, since the /etc/default/ script is still not getting sourced.

[muuki88]

@jasonmartens can you open a new issue with a small sample project demonstrating the case?