-
plone.protect-3.1.3-1.lbn25.noarch
This package contains utilities that can help to protect parts of Plone
or applications build on top of the Plone framework.
protect decorator
=================
The most common way to use plone.protect is through the 'protect'
decorator. This decorator takes a list of *checkers* as parameters: each
checker will check a specific security aspect of the request
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
plone.protect-3.1.3-1.lbn25.noarch
This package contains utilities that can help to protect parts of Plone
or applications build on top of the Plone framework.
protect decorator
=================
The most common way to use plone.protect is through the 'protect'
decorator. This decorator takes a list of *checkers* as parameters: each
checker will check a specific security aspect of the request
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
plone.recipe.alltests-1.3-1.lbn13.noarch
Buildout recipe for running tests isolated at package boundaries
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
plone.recipe.alltests-1.5.2-1.lbn19.noarch
Buildout recipe for running tests isolated at package boundaries
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
plone.recipe.alltests-1.5.2-1.lbn25.noarch
Buildout recipe for running tests isolated at package boundaries
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
plone.recipe.codeanalysis-1.0rc1-1.lbn19.noarch
Static code analysis for buildout-based Python projects.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
plone.recipe.codeanalysis-1.0rc1-1.lbn25.noarch
Introduction
plone.recipe.codeanalysis provides static code analysis for Buildout-based Python projects, including flake8,
JSHint, CSS Lint, and other code checks.
This buildout recipe creates a script to run the code analysis:
bin/code-analysis
By default plone.recipe.codeanalysis also creates a git pre-commit hook, in order to run the code analysis
automatically before each commit.
plone.recipe.codeanalysis comes with a Jenkins integration, that allows to use the same code analysis settings
on your local machine as well as on Jenkins.
plone.recipe.codeanalysis provides a Jenkins setting that allows to run it on a Jenkins CI server and to
process and integrate the output via the Jenkins Violations plugin.
Usually you do not want the recipe to create Jenkins output files on your local machine. Therefore it makes
sense to enable the Jenkins output only on the CI machine.
The Jenkins job itself should run "bin/code-analysis":
The Jenkins Violations plugin needs to be configured to read the output files generated by this configuration.
pep8 (to read the flake8 output):
**/parts/code-analysis/flake8.log
csslint:
**/parts/code-analysis/csslint.xml
jslint (to read the jshint output:
**/parts/code-analysis/jshint.xml
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
plone.recipe.zeoserver-1.2.6-1.lbn13.noarch
ZC Buildout recipe for installing a ZEO server
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
plone.recipe.zeoserver-1.3.1-1.lbn25.noarch
ZC Buildout recipe for installing a ZEO server
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
plone.recipe.zeoserver-1.3.1-1.lbn25.noarch
ZC Buildout recipe for installing a ZEO server
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
