Allow extension installs from a target destination

[Saelman]

Scope

CLI

Explanation

Allow extensions to be install from a different directory, for example /var/www/pterodactyl/blueprint or /extensions.
This would allow easier organizing of extensions.

Currently blueprint errors out when attempting to do this.

Is there an existing issue for this?

• I have searched the existing issues before opening this issue.

[Loki-101]

This would be beneficial. In the meantime, feel free to copy the logic in the Blueprint Docker Image (.helpers/listen.sh) that syncs .blueprint files between a designated extensions folder and your webroot if you need that functionality now @Saelman.