plone

zope-zc.buildout-2.12.2-1.lbn25.noarch
Buildout is a project designed to solve 2 problems: 1. Application-centric assembly and deployment Assembly runs the gamut from stitching together libraries to create a running program, to production deployment configuration of applications, and associated systems and tools (e.g. run-control scripts, cron jobs, logs, service registration, etc.). Buildout might be confused with build tools like make or ant, but it is a little higher level and might invoke systems like make or ant to get it's work done. Buildout might be confused with systems like puppet or chef, but it is more application focused. Systems like puppet or chef might use buildout to get their work done. Buildout is also somewhat Python-centric, even though it can be used to assemble and deploy non-python applications. It has some special features for assembling Python programs. It's scripted with Python, unlike, say puppet or chef, which are scripted with Ruby. 2. Repeatable assembly of programs from Python software distributions Buildout puts great effort toward making program assembly a highly repeatable process, whether in a very open-ended development mode, where dependency versions aren't locked down, or in a deployment environment where dependency versions are fully specified. You should be able to check buildout into a VCS and later check it out. Two checkouts built at the same time in the same environment should always give the same result, regardless of their history. Among other things, after a buildout, all dependencies should be at the most recent version consistent with any version specifications expressed in the buildout. Buildout supports applications consisting of multiple programs, with different programs in an application free to use different versions of Python distributions. This is in contrast with a Python installation (real or virtual), where, for any given distribution, there can only be one installed. To learn more about buildout, including how to use it, see http://buildout.org/.
Located in LBN / … / Plone and Zope / BastionLinux 25
rubygem-inspec-chef-0.3.4-1.lbn36.noarch
This plugin allows InSpec 'inputs' to be provided by Chef Server.
Located in LBN / … / DevOps / BastionLinux 36
python3-pytest-testinfra-6.8.0-1.fc36.noarch
With Testinfra you can write unit tests in Python to test actual state of your servers configured by management tools like Salt, Ansible, Puppet, Chef and so on. Testinfra aims to be a Serverspec equivalent in python and is written as a plugin to the powerful Pytest test engine.
Located in LBN / … / CI/CD / BastionLinux 36
goiardi-0.11.10-7.14dd4236.lbn36.x86_64
A Chef server written in Go, able to run entirely in memory, with optional persistence with saving the in-memory data to disk or using MySQL or Postgres as the data storage backend. Docs: http://goiardi.readthedocs.org/en/latest/index.html
Located in LBN / … / Cloud Computing / BastionLinux 36
rubygem-aws-sdk-opsworkscm-1.2.0-1.lbn36.noarch
Official AWS Ruby gem for AWS OpsWorks for Chef Automate (OpsWorksCM). This gem is part of the AWS SDK for Ruby.
Located in LBN / … / Cloud Computing / BastionLinux 36
password-reset-chef-2.0.4-3.lbn36.noarch
Reset Chef Web UI Admin password
Located in LBN / … / Cloud Computing / BastionLinux 36
zope-zc.buildout-2.1.0-1.lbn13.noarch
Buildout is a project designed to solve 2 problems: 1. Application-centric assembly and deployment Assembly runs the gamut from stitching together libraries to create a running program, to production deployment configuration of applications, and associated systems and tools (e.g. run-control scripts, cron jobs, logs, service registration, etc.). Buildout might be confused with build tools like make or ant, but it is a little higher level and might invoke systems like make or ant to get it's work done. Buildout might be confused with systems like puppet or chef, but it is more application focused. Systems like puppet or chef might use buildout to get their work done. Buildout is also somewhat Python-centric, even though it can be used to assemble and deploy non-python applications. It has some special features for assembling Python programs. It's scripted with Python, unlike, say puppet or chef, which are scripted with Ruby. 2. Repeatable assembly of programs from Python software distributions Buildout puts great effort toward making program assembly a highly repeatable process, whether in a very open-ended development mode, where dependency versions aren't locked down, or in a deployment environment where dependency versions are fully specified. You should be able to check buildout into a VCS and later check it out. Two checkouts built at the same time in the same environment should always give the same result, regardless of their history. Among other things, after a buildout, all dependencies should be at the most recent version consistent with any version specifications expressed in the buildout. Buildout supports applications consisting of multiple programs, with different programs in an application free to use different versions of Python distributions. This is in contrast with a Python installation (real or virtual), where, for any given distribution, there can only be one installed. To learn more about buildout, including how to use it, see http://buildout.org/.
Located in LBN / … / Plone and Zope / BastionLinux 13
rubygem-omniauth-chef-0.2.0-1.lbn25.noarch
OmniAuth strategy for Chef.
Located in LBN / … / Cloud Computing / BastionLinux 25
rubygem-omniauth-chef-oauth2-1.0.3-1.lbn25.noarch
OmniAuth OAuth2 strategy for Chef.
Located in LBN / … / Cloud Computing / BastionLinux 25
rubygem-poise-2.8.2-2.lbn25.noarch
Helpers for writing extensible Chef cookbooks.
Located in LBN / … / Cloud Computing / BastionLinux 25

« Previous 10 items Next 10 items » 1 ... 22 23 24 25 26 27 28 ... 48

Sections

Search results for chef


	Copyright © 2000-2024 Corporation of Balclutha Inc. All rights reserved.