New answers tagged

1

To make installers available to the customer services team: A simple web page providing all the installers for them to download and pass on to customers. To prevent customers installer another customer's application: You could use a simple customer based key either to enter in the installer or in the start screen of the app. The key doesn't have to be ...


1

Here is how I think of it, when it comes to software deployments. Application executables Structural Configuration and default settings Site Configuration User specific data To my mind, only the application executables and and the structural configuration should be managed within the installer - which is then able to be deployed to all sites. Sadly, ...


2

I assume that you have a base product, with some customization. A rollout for a specific customer would then be: pull base product from git pull and apply customization from git for the specified customer test in your test environment. The above should all be automated, so once the test passes, push the install out to a server which your technical services ...



Top 50 recent answers are included