Ansible
PS DSC
Downloads:
2,068
Downloads of v 1.8.1.2:
1,039
Last Update:
21 Sep 2014
Package Maintainer(s):
Software Author(s):
- Orchard Project
Tags:
orchardcms admin- Software Specific:
- Software Site
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Orchard Cms
- 1
- 2
- 3
1.8.1.2 | Updated: 21 Sep 2014
- Software Specific:
- Software Site
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
2,068
Downloads of v 1.8.1.2:
1,039
Maintainer(s):
Software Author(s):
- Orchard Project
Orchard Cms 1.8.1.2
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Orchard Project. The inclusion of Orchard Project trademark(s), if any, upon this webpage is solely to identify Orchard Project goods or services and not for commercial purposes.
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
Validation Testing Unknown
Verification Testing Passed
DetailsScan Testing Resulted in Flagged:
This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.
We recommend clicking the "Details" link to make your own decision on installing this package.
Deployment Method: Individual Install, Upgrade, & Uninstall
To install Orchard Cms, run the following command from the command line or from PowerShell:
To upgrade Orchard Cms, run the following command from the command line or from PowerShell:
To uninstall Orchard Cms, run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download orchardcms --internalize --source=https://community.chocolatey.org/api/v2/ -
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'" - Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade orchardcms -y --source="'INTERNAL REPO URL'" [other options]See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade orchardcms -y --source="'INTERNAL REPO URL'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install orchardcms
win_chocolatey:
name: orchardcms
version: '1.8.1.2'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'orchardcms' do
action :install
source 'INTERNAL REPO URL'
version '1.8.1.2'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller orchardcms
{
Name = "orchardcms"
Version = "1.8.1.2"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'orchardcms':
ensure => '1.8.1.2',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
This package was submitted prior to moderation and has not been approved. While it is likely safe for you, there is more risk involved.
Installs an instance of the Orchard Cms. Installs to c:\inetpub\wwwroot\orchard by default. See readme at http://github.com/andrewmyhre/chocolatey-OrchardCms
param(
[string][Parameter(Mandatory=$true,Position=1)]$WebsiteName,
[string][Parameter(Mandatory=$false,Position=2)]$VirtualPath="/",
[int][Parameter(Mandatory=$false,Position=3)]$Port=80,
[string][Parameter(Mandatory=$true,Position=4)]$InstallPath,
[string][Parameter(Mandatory=$true,Position=5)]$Source,
[string][Parameter(Mandatory=$false,Position=6)]$Username,
[string][Parameter(Mandatory=$false,Position=7)]$Password,
[string][Parameter(Mandatory=$false,Position=8)]$ApplicationName,
[switch]$allow32Bit,
[switch]$classicPipelineMode
)
Import-Module WebAdministration
if (!$ApplicationName)
{
$tmp="/default web site/orchard".split('/')
$ApplicationName=$tmp[$temp.length-1]
}
write-debug "Running install script with these options:"
write-debug "WebsiteName: $WebsiteName"
write-debug "VirtualPath: $VirtualPath"
write-debug "InstallPath: $InstallPath"
write-debug "Source: $Source"
write-debug "Username: $Username"
write-debug "Allow 32-bit: $allow32Bit"
write-debug "Classic pipeline mode: $classicPipelineMode"
if (!$Source)
{
$toolsFolder=$(Split-Path -parent $MyInvocation.MyCommand.Path)
$src = Join-Path $toolsFolder -ChildPath "application"
} else {
$src = $Source
}
write-debug "Installing from $src"
$appPool=get-item "IIS:\AppPools\$($ApplicationName)_pool" -ErrorAction SilentlyContinue
if (!$appPool)
{
$apppool = new-webapppool -Name "$($websiteName)_pool" -ErrorAction SilentlyContinue
write-host "Created application pool $($websiteName)_pool"
}
if (!(get-website -Name "$websiteName"))
{
write-debug "$websiteName not found, creating..."
if (!(test-path $installPath))
{
new-item $installPath -itemtype directory
write-host "Created directory $installPath"
}
if ($classicPipelineMode)
{
$appPool.managedPipelineMode = "Classic"
$appPool | set-item
write-host "Set application pool to classic pipeline mode"
}
new-website -Name "$websiteName" -Port $Port -PhysicalPath $installPath -ApplicationPool $appPool.name
write-host "Created website $websiteName"
if ($username -and $password)
{
# add user to IIS users group
net localgroup IIS_IUSRS /add orchard
Set-WebConfiguration "/system.applicationHost/sites/site[@name='$websiteName']/application[@path='/']/VirtualDirectory[@path='/']" -Value @{userName=$username;password=$password}
write-host "Set website logon to $username"
$apppool.processModel.username = $username
$apppool.processModel.password = $password
$apppool.processModel.identityType = 3
$apppool | set-item
write-Host "Set application pool identity to $username"
}
}
if ($virtualPath -ne "/")
{
if (!(get-webapplication -Site "$websiteName" -Name $virtualPath.TrimStart("/")))
{
write-debug "creating virtual app $($virtualPath.TrimStart("/")) in $websiteName at $installPath"
if (!(test-path $installPath)) { new-item -path $installPath -itemtype directory }
new-webapplication -Name $virtualPath.TrimStart("/") -Site $websiteName -PhysicalPath $installPath -ApplicationPool $appPool.name
}
if ($username -and $password)
{
# add user to IIS users group
net localgroup IIS_IUSRS /add orchard
Set-WebConfiguration "/system.applicationHost/sites/site[@name='$websiteName']/application[@path='$virtualPath']/VirtualDirectory[@path='/']" -Value @{userName=$username;password=$password}
write-host "Set application logon to $username"
$apppool.processModel.username = $username
$apppool.processModel.password = $password
$apppool.processModel.identityType = 3
$apppool | set-item
write-Host "Set application pool identity to $username"
}
}
if (!(test-path "c:\Program Files\IIS\Microsoft Web Deploy V3\msdeploy.exe")){
chocolatey install webdeploy
}
write-debug "preparing to run msdeploy"
$destPath = $websiteName
if ($virtualPath -ne "/") { $destPath += $virtualPath }
$args = @()
$args += "-verb:sync"
$args += "-source:contentPath='$src'"
$args += "-dest:contentPath='$destPath'"
write-debug """c:\Program Files\IIS\Microsoft Web Deploy V3\msdeploy.exe"" $args"
$deployProcess=(start-process "c:\Program Files\IIS\Microsoft Web Deploy V3\msdeploy.exe" -argumentlist $args -PassThru -wait -nonewwindow)
write-host "Exit code: $($deployProcess.ExitCode)"
if ($deployProcess.ExitCode -ne 0)
{
throw "MSDeploy failed with exit code $($deployProcess.ExitCode)"
}
if ($allow32Bit)
{
set-webconfiguration "/system.applicationHost/applicationPools/add[@name='$($appPool.Name)']/@enable32BitAppOnWin64" -Value "true"
write-host "Set application pool to allow 32-bit applications"
}
# create a firewall rule
if (!(netsh advfirewall firewall show rule name="$packageName" | select-string "$packageName"))
{
netsh advfirewall firewall add rule name="$packageName" dir=in action=allow protocol=TCP localport=$port enable=yes
}Log in or click on link to see number of positives.
- OrchardCms.1.8.1.2.nupkg (f131f9e69dab) - ## / 56
- Orchard.Web.1.8.1.zip (02f1eb855472) - ## / 48
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
| Add to Builder | Version | Downloads | Last Updated | Status |
|---|---|---|---|---|
| Orchard Cms 1.8.1.2 | 1039 | Sunday, September 21, 2014 | Unknown | |
| Orchard Cms 1.8.1.1 | 394 | Friday, September 19, 2014 | Unknown | |
| Orchard Cms 1.8.1 | 453 | Friday, September 19, 2014 | Unknown |
This package has no dependencies.
Ground Rules:
- This discussion is only about Orchard Cms and the Orchard Cms package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or Orchard Cms, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.