Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added Customizing option for setup.exe bootstrapper #1248

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

schwarzr
Copy link

@schwarzr schwarzr commented Feb 2, 2018

We are trying to use Squirrel as the Deployment solution for a SaaS based application. In order to connect to the right database or service we need a very small but important configuration switch in the application, a tenant key. I was looking for ways to inject this configuration without having to call --releasify multiple times, because there could be hundreds of possible target environments.

So what we are trying to do now, is to customize the installer on the fly when it is downloaded from our website. I'm doing this by temporarily copying the setup exe, calling rcedit.exe --set-version-string "SpecialBuild" "MyTenantKey" and resigning it. Also for larger automated deployments we allowed to pass this SpecialBuild argument as a commandline parameter for the setup.exe.
so setting the special build attribute with rcedit and applying --special-build "MyTenantKey" as a commandline argument form setup.exe has the same effect.

When sucha specialbuild argument is passed i set an Environment Variable SQUIRREL_SPECIAL_BUILD and within my OnInitialIntall handler i can access this Information an store it in the UserConfig.

For now i'm using the --bootstrapperExe as a switch for squirrel.exe --releasify and pass my custom setup.exe, but because other people are also asking for a way to pass information through the initial setup to the app and because it doesn't change the existing behavior of your bootstrapper you might want to merge my changes to your project.

Might solve #487 as well.

…ronment Variable SQUIRREL_SPECIAL_BUILD on initial install.
@shiftkey shiftkey added the unmergeable Pull requests that do not merge currently into the default branch label Apr 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
unmergeable Pull requests that do not merge currently into the default branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants