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
I believe that presently the start script is always named by the release name.
It would be helpful to have a config option to modify the name of the script to give it a custom name in case there is some naming ambiguity with other executables on a system.
E.g.:
{start_script_name, Name}.
The text was updated successfully, but these errors were encountered:
I don't know that there would be major problems with this as long as there can remain canonical names (which include the release version) to prevent some clashes since there's currently two releases created. This could be a welcome feature I think.
I believe that presently the start script is always named by the release name.
It would be helpful to have a config option to modify the name of the script to give it a custom name in case there is some naming ambiguity with other executables on a system.
E.g.:
The text was updated successfully, but these errors were encountered: