Improve CLI configuration

[ccarney16]

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 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.

[prplwtf]

Somehow missed this, would you like me to look into this for this release?

About the /app for panel files; as far as I know this is the standard directory for running Pterodactyl in Docker. I'm not sure why someone would want to change that but I can look into it.

[ccarney16]

Yeah, that would be great to look into it for the next release.

As for /app, I've been making a semi custom container deployment project for the last several years in attempt to fix shortcomings of the original version of the image. Blueprint also mucks with /storage which I need to look further into as I do have that in a volume to make it persistent (Which was another issue with the original image years ago that relied on having eggs and other variable data in /storage). You can see my container images at https://github.com/ccarney16/pterodactyl-containers.

Lastly I've been lately diving into the code a bit more since I've been getting requests to make a blueprint version of my images. I am curious as to why docker needs to be detected and to modify the base script's behavior?

[prplwtf]

Modified script behavior had to do something with Blueprint Docker. I don't remember specifics.

I have added a line of code to blueprint.sh which sources a .blueprintrc file. This should allow overriding variables from outside of the blueprint.sh file. I am unable to create a more in-depth implementation for next release.

The .blueprintrc file is sourced below the docker if-statement.