Hi all,
How would you feel about not having to scrounge the executables off an existing deployment package to make it work?
It would seem trivial to have the executables delivered along with the SF as part of the database, and have them written to disk at the same time as the other scripts.
So, when looting is your thing, ignore this post. Otherwise, upvote to stop ransacking retired deployment packages.
+23The Software Factory cannot create a deployment package with the Thinkwise deployer as both product have different release cycles. This would mean the version of the Deployer that is used becomes an older version more often than not.
The Deployer also has the added benefit of being able to update Indicium and install Runtime components on the Web server. This would make it far out of scope for a deployment package created with the SF.
Usually deployments are done using a tool such as Octopus deployer. In this tool you can combine the new deployment package script with all kinds of other events to deploy the complete application at the designated spot. There's another idea of allowing the download of runtime components through an API. This way it would be even more easy to get the latest version of the Thinkwise deployer and use it to deploy your application. I'll merge this idea to that.
+23Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
