digi-approval:数字堪培拉挑战赛 - 审批系统

  • C7_719353
    了解作者
  • 6MB
    文件大小
  • zip
    文件格式
  • 0
    收藏次数
  • VIP专享
    资源类型
  • 0
    下载次数
  • 2022-04-30 06:52
    上传日期
数码审批 DigiApproval 是一种基于 Web 的概念验证业务工作流工具,是作为 ACT 政府的入口而开发的。 版权 版权所有 :copyright: 2013-2015 DigiACTive 团队(Daniel Axtens、Benjamin Roberts、Andrew Donnellan)。 该程序是免费软件:您可以根据自由软件基金会发布的 GNU 通用公共许可证(许可证的第 3 版或(由您选择)任何更高版本)的条款重新分发和/或修改它。 分发此程序是希望它有用,但不作任何保证; 甚至没有对适销性或针对特定目的的适用性的暗示保证。 有关更多详细信息,请参阅 GNU 通用公共许可证。 您应该已经收到一份 GNU 通用公共许可证以及该程序。 如果没有,请参阅 。
digi-approval-develop.zip
内容介绍
Windows Cookbook ================ Provides a set of Windows-specific primitives (Chef resources) meant to aid in the creation of cookbooks/recipes targeting the Windows platform. Requirements ------------- Version 1.3.0+ of this cookbook requires Chef 0.10.10+. ### Platforms * Windows XP * Windows Vista * Windows Server 2003 R2 * Windows 7 * Windows Server 2008 (R1, R2) The `windows_task` LWRP requires Windows Server 2008 due to its API usage. ### Cookbooks The following cookbooks provided by Opscode are required as noted: * chef_handler (`windows::reboot_handler` leverages the chef_handler LWRP) * powershell - The Printer and Printer Port LWRP require Powershell. **NOTE** We cannot specifically depend on Opscode's powershell, because powershell depends on this cookbook. Ensure that `recipe[powershell]` exists in the node's expanded run list so it gets downloaded where the printer LWRPs are used. Attributes ---------- * `node['windows']['allow_pending_reboots']` - used to configure the `WindowsRebootHandler` (via the `windows::reboot_handler` recipe) to act on pending reboots. default is true (ie act on pending reboots). The value of this attribute only has an effect if the `windows::reboot_handler` is in a node's run list. Resource/Provider ----------------- ### windows_auto_run #### Actions - :create: Create an item to be run at login - :remove: Remove an item that was previously setup to run at login #### Attribute Parameters - :name: Name attribute. The name of the value to be stored in the registry - :program: The program to be run at login - :args: The arguments for the program #### Examples Run BGInfo at login ```ruby windows_auto_run 'BGINFO' do program 'C:/Sysinternals/bginfo.exe' args '\'C:/Sysinternals/Config.bgi\' /NOLICPROMPT /TIMER:0' not_if { Registry.value_exists?(AUTO_RUN_KEY, 'BGINFO') } action :create end ``` ### windows_batch (Chef 11.6.0 includes a built-in [batch](http://docs.opscode.com/resource_batch.html) resource, so use that in preference to `windows_batch` if possible.) Execute a batch script using the cmd.exe interpreter (much like the script resources for bash, csh, powershell, perl, python and ruby). A temporary file is created and executed like other script resources, rather than run inline. By their nature, Script resources are not idempotent, as they are completely up to the user's imagination. Use the `not_if` or `only_if` meta parameters to guard the resource for idempotence. #### Actions - :run: run the batch file #### Attribute Parameters - command: name attribute. Name of the command to execute. - code: quoted string of code to execute. - creates: a file this command creates - if the file exists, the command will not be run. - cwd: current working directory to run the command from. - flags: command line flags to pass to the interpreter when invoking. - user: A user name or user ID that we should change to before running this command. - group: A group name or group ID that we should change to before running this command. #### Examples ```ruby windows_batch 'unzip_and_move_ruby' do code <<-EOH 7z.exe x #{Chef::Config[:file_cache_path]}/ruby-1.8.7-p352-i386-mingw32.7z -oC:\\source -r -y xcopy C:\\source\\ruby-1.8.7-p352-i386-mingw32 C:\\ruby /e /y EOH end ``` ```ruby windows_batch 'echo some env vars' do code <<-EOH echo %TEMP% echo %SYSTEMDRIVE% echo %PATH% echo %WINDIR% EOH end ``` ### windows_feature Windows Roles and Features can be thought of as built-in operating system packages that ship with the OS. A server role is a set of software programs that, when they are installed and properly configured, lets a computer perform a specific function for multiple users or other computers within a network. A Role can have multiple Role Services that provide functionality to the Role. Role services are software programs that provide the functionality of a role. Features are software programs that, although they are not directly parts of roles, can support or augment the functionality of one or more roles, or improve the functionality of the server, regardless of which roles are installed. Collectively we refer to all of these attributes as 'features'. This resource allows you to manage these 'features' in an unattended, idempotent way. There are two providers for the `windows_features` which map into Microsoft's two major tools for managing roles/features: [Deployment Image Servicing and Management (DISM)](http://msdn.microsoft.com/en-us/library/dd371719(v=vs.85).aspx) and [Servermanagercmd](http://technet.microsoft.com/en-us/library/ee344834(WS.10).aspx) (The CLI for Server Manager). As Servermanagercmd is deprecated, Chef will set the default provider to `Chef::Provider::WindowsFeature::DISM` if DISM is present on the system being configured. The default provider will fall back to `Chef::Provider::WindowsFeature::ServerManagerCmd`. For more information on Roles, Role Services and Features see the [Microsoft TechNet article on the topic](http://technet.microsoft.com/en-us/library/cc754923.aspx). For a complete list of all features that are available on a node type either of the following commands at a command prompt: ```text dism /online /Get-Features servermanagercmd -query ``` #### Actions - :install: install a Windows role/feature - :remove: remove a Windows role/feature #### Attribute Parameters - feature_name: name of the feature/role to install. The same feature may have different names depending on the provider used (ie DHCPServer vs DHCP; DNS-Server-Full-Role vs DNS). #### Providers - **Chef::Provider::WindowsFeature::DISM**: Uses Deployment Image Servicing and Management (DISM) to manage roles/features. - **Chef::Provider::WindowsFeature::ServerManagerCmd**: Uses Server Manager to manage roles/features. #### Examples Enable the node as a DHCP Server ```ruby windows_feature 'DHCPServer' do action :install end ``` Enable TFTP ```ruby windows_feature 'TFTP' do action :install end ``` Disable Telnet client/server ```ruby %w[TelnetServer TelnetClient].each do |feature| windows_feature feature do action :remove end end ``` ### windows_package Manage Windows application packages in an unattended, idempotent way. The following application installers are currently supported: * MSI packages * InstallShield * Wise InstallMaster * Inno Setup * Nullsoft Scriptable Install System If the proper installer type is not passed into the resource's installer_type attribute, the provider will do it's best to identify the type by introspecting the installation package. If the installation type cannot be properly identified the `:custom` value can be passed into the installer_type attribute along with the proper flags for silent/quiet installation (using the `options` attribute..see example below). __PLEASE NOTE__ - For proper idempotence the resource's `package_name` should be the same as the 'DisplayName' registry value in the uninstallation data that is created during package installation. The easiest way to definitively find the proper 'DisplayName' value is to install the package on a machine and search for the uninstall information under the following registry keys: * `HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall` * `HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall` * `HKEY_LOCAL_MACHINE\Software\Wow6464Node\Microsoft\Windows\CurrentVersion\Uninstall` For maximum flexibility the `source` attribute supports both remote and local installation packages. #### Actions - :install: install a package - :remove: remove a package. The remove action is completely hit or miss as many application uninstallers do not support a full silent/quiet mode. #### Attribute Parameters - package_name: name attribute. The 'DisplayName' of the application installation package. - source: The source of the windows installer. This can either be a URI or a local path. - installer_type: They type of windo
评论
    相关推荐
    • periodical:日历来跟踪您的月经并计算可能的肥沃日子
      期刊 日历来跟踪您的月经并计算可能的肥沃日子 ... 该程序是免费软件:您可以根据自由软件基金会发布的GNU通用公共许可证的条款(许可证的版本3)或(根据您的选择)任何更高版本来重新分发和/或修改它。 分发该程序是
    • Gnubert Peer to Peer Evolution-开源
      Gnubert 将是一个系统,可以利用互联网上许多计算机的能力来解决使用进化技术的问题。 任何用户都可以定义一个问题,系统将尝试解决它。
    • GNU/Liberty Basic Compiler Collection-开源
      GLBCC是GNU编译器集合的前端。 GLBCC将Liberty Basic添加到GCC语言集合中,以便Liberty Basic代码可以直接编译为可执行文件。 由于GLBCC使用GCC,因此目标文件也可以与目标文件链接
    • admb:广告模型制作工具
      ADMB项目 ADMB-12.3 2021年3月7日发行 概述 ADMB(自动差分模型生成器)软件套件是用于非线性统计建模的环境,可实现快速的模型开发,数值稳定性,快速高效的计算以及高精度的参数估计。 AD Model Builder是围绕...
    • vs Cobol screen handler-开源
      vs Cobol屏幕处理程序将使用简单的元语言(使用标准文本文件)定义的屏幕转换为Cobol源代码,可以使用PERFORM语句进行访问。... 您可以根据自由软件基金会发布的GNU通用公共许可证v2.0的条款重新分发和/或修改它。
    • cuBERT:直接在NVIDIA(CUDA,CUBLAS)和Intel MKL上快速实现BERT推理
      直接在NVIDIA(CUDA,CUBLAS)和Intel MKL上快速实现BERT推理 直接在NVIDIA(CUDA,... Debian GNU / Linux 8(jessie) gcc(Debian 4.9.2-10 + deb8u1)4.9.2 CUDA:版本9.0,V9.0.176 MKL:2019.0.1.20181227
    • imb-encoder:用于编码 USPS IMB 跟踪号的库
      imb 编码器 这个库的目的是接收一个信息的对象并返回编码后的字符串。 用法 var encoder = require ( 'imb-encoder' ) ; var encodedString = encoder . encodeTrackingNumber ( ... 此逻辑归功于上的 Robert Mathews
    • java校招笔试题-programmer:如何成为一名程序员,罗伯特·里德
      该许可证的副本包含在标题为“GNU 自由文档许可证”的部分中。 2002年 奉献 致 Hire.com 的程序员。 目录 介绍 初学者个人技能 学习调试 如何通过拆分问题空间进行调试 如何消除错误 如何使用日志进行调试 如何理解...
    • robertbrignull-dependabot-test
      robertbrignull-dependabot-test
    • SIM800C_MQTT.rar
      使用SIM800C模块,使用MQTT协议,连接中国移动onenet平台,能实现数据的订阅、发布、存储等