Introduction
This is the plone.org site package and corresponding buildout. It is used to power http://plone.org. It is also a great buildut for working on developing Plone.org centric products such as PloneSoftwareCenter, PloneHelpCenter, and PloneServicesCenter.
Code repository: http://svn.plone.org/svn/plone/Products.PloneOrg
Questions and comments to admins@lists.plone.org
Report bugs to admins@lists.plone.org
The current supported version of Plone is: 4.1.x.
Production
The default buildout setup is for setting up a production environment, including Plone and nginx running under supervisor. (This won’t be functional without extra work, as other parts of the plone.org stack such as the load balancer are not currently in the buildout.) Run buildout as normal:
$ python2.6 bootstrap.py $ bin/buildout $ sudo bin/supervisord
Development
To build plone.org for development, comment out the line in buildout.cfg that says ‘conf/production.cfg’ and uncomment ‘conf/develop.cfg’. Then proceed as normal:
$ python2.6 bootstrap.py $ bin/buildout $ bin/instance fg
This will get you an unthemed copy of the site. If you want to work on the theme, you can build Plone + nginx by modifying buildout.cfg to use conf/develop_theme.cfg, and then run:
$ python2.6 bootstrap.py $ bin/buildout $ bin/instance fg $ parts/nginx/sbin/nginx -c ../../etc/nginx.conf
The unthemed site is at http://localhost:8080. Go there and add a Plone site with the id ‘plone.org’. The themed site is at http://localhost:5021/.
NOTE: Due to circumstances around testing the PloneOrg module, there are 2 directories with svn info. The source for Products.PloneOrg is in the ‘src’ directory and the rest of the checked out packages are in ‘sources’. If you can’t find a checkout, double check BOTH directories.
Database
To get the latest databases from plone.org, you just need to run the get_data shell script. It assumes rsync is in your path:
$ ./conf/get_data
(This requires shell access to plone.org.)
Changelog
1.4 - May 13, 2011
Clean up and release [aclark]
1.3 - Feb 10, 2011
Fix the team template portlet rendering. [rossp]
Rework buildouts, developer docs [davisagli, eleddy]
1.2 - Dec 8, 2009
Add a css rule to make the highlighted text inside <pre>s readable. Fixes http://dev.plone.org/plone.org/ticket/1743. [dukebody]
1.1 - Dec 3, 2009
Fix broken jquery-ui-accordion.js
1.0 - Nov 23, 2009
Initial release [aclark]
Metadata
Release files for Products.PloneOrg 1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| Products.PloneOrg-1.4.zip | 891.8 kB | Without provenance | Details |
Release files / Products.PloneOrg-1.4.zip
| Download URL | Products.PloneOrg-1.4.zip |
|---|---|
| Size | 891.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
488ff9a5aa35f99fa358d3982610148e90f71a4adbdd31eff54973b250b79794
|
|
BLAKE2b-256 checksum How to use checksums |
a0aebc4700eea44a9387e52525005f7eb8114a2c511e564384fb190a7cef16c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Products.PloneOrg 1.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.