Single envfile for customizations

immense / Remotely

A remote control and remote scripting solution, built with .NET 8, Blazor, and SignalR.

GNU General Public License v3.0

4.55k stars 1.61k forks source link

Single envfile for customizations #542

Open osnipezzini opened 1 year ago

osnipezzini commented 1 year ago

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"

modem7 commented 1 year ago

I've suggested some further variables here: https://github.com/immense/Remotely/issues/590

osnipezzini commented 1 year ago

I've suggested some further variables here: #590

Is not what i want.

I opened this issue for clients that want your custom build. I wanna use a different portable filename per example. And if we have 2 companies connectiong to 1 client ?

And i wanna build all clients with server url embedded in bin files

If 2 distincts companies offer support on same client per example:

They want to install a unattended service. They can't because service has same name, and files and folders has same name too

osnipezzini commented 1 year ago

Here by example: Why don't use a const for APP_NAME amd filenames too.

Maybe i can start a pull request with this