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
Hello, I am writing this feature request because I think that the CLI installation process can be improved upon.
I am working on a docker image and have found out that the install script is hard coded with variables and functions that make working with blueprint a bit more tedious on the command line. My proposal is for the script to set default values that can be overridden. An example would be to replace WEBUSER with : ${WEBUSER:="www-data"}. This will set the value only if it was not defined prior. This should also be compatible with both bash and similar shells but I've only confirmed this working on bash and alpine ash. Additionally you can also do configuration files like this by sourcing where the script is located source "$(dirname $0)/some.config".
Also as a side note for docker, I do not use /app for the panel files. If this can be modified down the road so it can be a configurable, that would be great.
Is there an existing issue for this?
I have searched the existing issues before opening this issue.
The text was updated successfully, but these errors were encountered:
Scope
CLI
Explanation
Hello, I am writing this feature request because I think that the CLI installation process can be improved upon.
I am working on a docker image and have found out that the install script is hard coded with variables and functions that make working with blueprint a bit more tedious on the command line. My proposal is for the script to set default values that can be overridden. An example would be to replace WEBUSER with
: ${WEBUSER:="www-data"}
. This will set the value only if it was not defined prior. This should also be compatible with both bash and similar shells but I've only confirmed this working on bash and alpine ash. Additionally you can also do configuration files like this by sourcing where the script is locatedsource "$(dirname $0)/some.config"
.Also as a side note for docker, I do not use
/app
for the panel files. If this can be modified down the road so it can be a configurable, that would be great.Is there an existing issue for this?
The text was updated successfully, but these errors were encountered: