Single envfile for customizations

**Is your feature request related to a problem? Please describe.**
No

**Describe the solution you'd like**
It's a common behavior for some companies change name of the executables, maybe for branding or just for security issues.
Imagine 2 companies using same remote software. So we have a conflict, because one company conflict with another.

With this, we are able to customize name of files, directories and more of the software

** Examples
- APPNAME = "Remotely"
- BASEURL = "https://support.remotely.site"

The issue names no files, tests, or entry points. Start by locating where executable names, directory names, and deployment configuration are defined, then assess whether one environment file can control the requested customizations. Done means the supported names and the BASEURL can be changed from one documented configuration source.

Written by the indexing model from the issue text.