On Fri, Jun 26, 2015 at 1:57 AM, Mike A. wrote:
If there's no way I can use Puppet to install/update Tomcat directly,
should I use Chocolatey instead?
You can use Puppet to upgrade Tomcat directly. You've probably already come
across puppetlabs-tomcat[1] and realized it isn't quite set up for Windows.
You've probably also noticed that none of the tomcat modules on the forge
advertise working with Windows[2]. It seems one could look at the steps
required to update tomcat and create a module that will do so, or
contribute back to puppetlabs-tomcat the Windows requirements.
[1]
https://forge.puppetlabs.com/puppetlabs/tomcat[2]
https://forge.puppetlabs.com/tags/tomcat?utf-8=%E2%9C%93&os=windowsHow reliable is Chocolatey in a production server?
Depending on your methodology, reliable. Provided you:
- Create your own packages that
- Vendor the installers somewhere in your network and
- You host your own internal chocolatey repository[3]
The most important thing in here is production usage != community feed (
https://chocolatey.org).You can start with a copy of the package, then adjust the urls to your
internal ones - see
https://chocolatey.org/packages/Tomcat#files and take a
look at the scripts. Download the zip files to a CIFS share or embed them
in the package itself. Then adjust the links in the package itself.
The package itself has a download link on the left, you can download the
nupkg and rename to .zip and treat it as a regular zipped file. Then when
you are ready, just use choco pack to repack the files into a nupkg and
push it up to your internal repository.
[3]
https://github.com/chocolatey/choco/wiki/How-To-Host-Feed
