Skip to main content

This zc.buildout recipe installs an OS X, wxPython-based visual controller for Plone.

Typical usage in a Plone buildout:

parts=
    ...
    osxcontroller
    ...

[osxcontroller]
recipe = plone.recipe.osxcontroller

Detailed Documentation

Example usage

We’ll start by creating a buildout that uses the recipe:

>>> write('buildout.cfg',
... """
... [buildout]
... parts = controller
...
... [controller]
... recipe = plone.recipe.osxcontroller
... """)

Running the buildout gives us:

>>> print 'start', system(buildout)
start...
Installing controller.
<BLANKLINE>

Let’s look for the symlinks to our app:

>>> ls(sample_buildout)
-  .installed.cfg
d  PloneController.app
d  bin
-  buildout.cfg
d  develop-eggs
d  eggs
d  parts

Contributors

Steve McMahon, Author

Change history

0.4 (2010-03-15)

  • Adapt to Plone 4 by removing separate buttons for viewing Plone and Zope.

0.3 (2009-09-08)

  • Change wait times to account for odd status replies

0.2 (2008-12-16)

  • Change to copy controller app to dest [Steve McMahon].

0.1 (2008-11-30)

  • First release [Steve McMahon].

Metadata

Release files for plone.recipe.osxcontroller 0.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for plone.recipe.osxcontroller 0.4
File Size Uploaded Provenance Actions
plone.recipe.osxcontroller-0.4.zip 331.9 kB Without provenance Details for plone.recipe.osxcontroller-0.4.zip

Release files / plone.recipe.osxcontroller-0.4.zip

Download URL plone.recipe.osxcontroller-0.4.zip
Size 331.9 kB
Tags Source
SHA-256 checksum
How to use checksums
481df3ba10fd8cca4391615dfd4ebffc6391553451283f3f3374953f64817f22
BLAKE2b-256 checksum
How to use checksums
4b0014c9b86a3bd5e0d02f5c20e7af306bbd7cd9f46c28ba44634d7d1a3e831f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for plone.recipe.osxcontroller 0.4

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.4 This release

1 release file No provenance

0.1

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page