Search results

archetypes.querywidget-1.0.10-1.lbn13.noarch

archetypes.querywidget

archetypes.querywidget-1.1.3-1.lbn25.noarch

archetypes.querywidget

archetypes.querywidget-1.1.3-1.lbn25.noarch

archetypes.querywidget

archetypes.referencebrowserwidget-2.4.20-1.lbn13.noarch

This is an implementation of referencebrowser widget. It provides a widget used for Archetypes reference-fields. The widget can be used on its own or as a dropin replacement of the ATReferenceBrowserWidget in Plone 3 and is included in Plone >= 4. Unlike the ATReferenceBrowserWidget, archetypes.refencebrowserwidget uses an overlay instead of a popup to display the referencebrowser.

archetypes.referencebrowserwidget-2.5.10-1.lbn25.noarch

This is an implementation of referencebrowser widget. It provides a widget used for Archetypes reference-fields. The widget can be used on its own or as a dropin replacement of the ATReferenceBrowserWidget in Plone 3 and is included in Plone >= 4. Unlike the ATReferenceBrowserWidget, archetypes.refencebrowserwidget uses an overlay instead of a popup to display the referencebrowser.

archetypes.referencebrowserwidget-2.5.11-1.lbn25.noarch

This is an implementation of referencebrowser widget. It provides a widget used for Archetypes reference-fields. The widget can be used on its own or as a dropin replacement of the ATReferenceBrowserWidget in Plone 3 and is included in Plone >= 4. Unlike the ATReferenceBrowserWidget, archetypes.refencebrowserwidget uses an overlay instead of a popup to display the referencebrowser.

archetypes.schemaextender-2.1.2-1.lbn13.noarch

This package allows you to modify an Archetypes schema, using simple adapters. This can be used to add new fields, reorder fields and fieldsets or make other changes. The most common use of schema extension is to allow add-on products to enhance standard Plone content types, for example by adding an option that can be set to toggle special behaviour. schemaextender hooks into the Archetypes framework by registering an ISchema adapter for BaseContent and BaseFolder, making it responsible for providing the schema for all types derived from those classes. This includes all standard Plone content types. Since only one ISchema adapter can be active schemaextender provides its own mechanism to modify schemas using named adapters. There are three types of adapters available: * ISchemaExtender: using this adapter you can add new fields to a schema. * IOrderableSchemaExtender: this adapters makes it possible to both add new fields and reorder fields. This is more costly than just adding new fields. * IBrowserLayerAwareExtender: this adpaters are making use of plone.browserlayer, so that the extender is only available if a layer is registered. * ISchemaModifier: this is a low-level hook that allows direct manipulation of the schema. This can be very dangerous and should never be used. The adapter types are documented in the ''interfaces.py'' file in archetypes.schemaextender.

archetypes.schemaextender-2.1.8-1.lbn25.noarch

This package allows you to modify an Archetypes schema, using simple adapters. This can be used to add new fields, reorder fields and fieldsets or make other changes. The most common use of schema extension is to allow add-on products to enhance standard Plone content types, for example by adding an option that can be set to toggle special behaviour. schemaextender hooks into the Archetypes framework by registering an ISchema adapter for BaseContent and BaseFolder, making it responsible for providing the schema for all types derived from those classes. This includes all standard Plone content types. Since only one ISchema adapter can be active schemaextender provides its own mechanism to modify schemas using named adapters. There are three types of adapters available: * ISchemaExtender: using this adapter you can add new fields to a schema. * IOrderableSchemaExtender: this adapters makes it possible to both add new fields and reorder fields. This is more costly than just adding new fields. * IBrowserLayerAwareExtender: this adpaters are making use of plone.browserlayer, so that the extender is only available if a layer is registered. * ISchemaModifier: this is a low-level hook that allows direct manipulation of the schema. This can be very dangerous and should never be used. The adapter types are documented in the ''interfaces.py'' file in archetypes.schemaextender.

archetypes.schemaextender-2.1.8-1.lbn25.noarch

This package allows you to modify an Archetypes schema, using simple adapters. This can be used to add new fields, reorder fields and fieldsets or make other changes. The most common use of schema extension is to allow add-on products to enhance standard Plone content types, for example by adding an option that can be set to toggle special behaviour. schemaextender hooks into the Archetypes framework by registering an ISchema adapter for BaseContent and BaseFolder, making it responsible for providing the schema for all types derived from those classes. This includes all standard Plone content types. Since only one ISchema adapter can be active schemaextender provides its own mechanism to modify schemas using named adapters. There are three types of adapters available: * ISchemaExtender: using this adapter you can add new fields to a schema. * IOrderableSchemaExtender: this adapters makes it possible to both add new fields and reorder fields. This is more costly than just adding new fields. * IBrowserLayerAwareExtender: this adpaters are making use of plone.browserlayer, so that the extender is only available if a layer is registered. * ISchemaModifier: this is a low-level hook that allows direct manipulation of the schema. This can be very dangerous and should never be used. The adapter types are documented in the ''interfaces.py'' file in archetypes.schemaextender.

argocd-autopilot-0.4.19-1.1.lbn36.x86_64

New users to GitOps and Argo CD are not often sure how they should structure their repos, add applications, promote apps across environments, and manage the Argo CD installation itself using GitOps. Argo CD Autopilot saves operators time by: * Installing and managing the Argo CD application using GitOps. * Providing a clear structure for how applications are to be added and updated, all from git. * Creating a simple pattern for making updates to applications and promoting those changes across environments. * Enabling better disaster recovery by being able to bootstrap new clusters with all the applications previously installed. * Handling secrets for Argo CD to prevent them from spilling into plaintext git. (Soon to come) The Argo-CD Autopilot is a tool which offers an opinionated way of installing Argo-CD and managing GitOps repositories.