Deploy Plone site to static files.
Project description
Overview
stxnext.staticdeployment is a tool to deploy Plone site to static files. It supporst Plone 3 and Plone 4 (including sites using Diazo themes).
Installation
Edit buildout.cfg and append stxnext.staticdeployment to eggs and zcml parameters in instance section:
[instance] eggs = ... stxnext.staticdeployment zcml = ... stxnext.staticdeployment
Instance must be rebuild and restarted:
./bin/buildout ./bin/instance stop ./bin/instance start
This product must be also installed inside Plone site. Do do it, go to Site Setup -> Add/Remove Products, select checkbox near stxnext.staticdeployment and click Install button.
Configuration
Every website has own configuration (different set of eggs, skin, products etc.) - this I meas as project. But website can have few instances (development, test and production instances). Because of this, configuration is split for two parts:
instance parameters:
parameters connected to instance - e.g.: domain
configured in Control Panel - can be edited throw the web (Site Setup -> Static deployment -> Settings tab)
form has description and validation - can be used by less experienced users
website parameters:
stored in INI file
created by developer of website
can be used by many sites
default configuration (included in egg)
default configuration can be overriden by file ${buildout:directory}/etc/staticdeployment.ini
staticdeployment.ini paramaters
- deployment-directory (string)
Where to deploy site. Path can be relative or absolute. Default: ./plone-static
- layer-interface (string)
Default: zope.publisher.interfaces.browser.IDefaultBrowserLayer
- defaultskin-name (string)
Skin which will be used during deploy. Default: Sunburst Theme
- deploy-plonesite (boolean)
If enabled home page will be deployed also as index.html in root of deployment-directory. Default: true
- deploy-registry-files (boolean)
Deploy registry files (CSS, JS, KSS)? Default: true
- make-links-relative (boolean)
Make all links relative (otherwise they will be absolute). Default: false
- add-index (boolean)
Add index.html to all links (that should have index.html). Works only when make-links-relative is enabled. Default: false
- page-types (list)
Page types that should be deployed. For example: ATDocument, ATFolder
- file-types (list)
File types that should be deployed. For example: ATBlob
- skinstool-files (list)
Additional files (from plone_skins tool) which should be deployed. For example: plone_images/favicon.ico
- additional-files (list)
Other files to deploy. For example: sitemap.xml.gz
- additional-pages (list)
Other pages that should be deployed. For example: sitemap
- deployable-review-states (list)
Only pages with review states listed here will be deployed. Default: published
Usage
When website is ready to deployment go to Site Setup -> Static deployment -> Deployment tab. Select Deploy static version of website checkbox and press Save button. Deployment will work for few seconds or minutes (it depends on size of website and server performance).
Changelog
1.0.0 (23.05.2012)
Code refactoring
Compatibility with Plone 3
Created tests
Added possibility of generating relative paths
History of earlier changes: https://github.com/stxnext/stxnext.staticdeployment/blob/refactoring/docs/OLD_HISTORY.txt
Project details
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
File details
Details for the file stxnext.staticdeployment-1.0.0.tar.gz
.
File metadata
- Download URL: stxnext.staticdeployment-1.0.0.tar.gz
- Upload date:
- Size: 42.7 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 2c504ca3c33887c895c328fe2fdf7e426020905f7c10f6f4c2d6c9c4828a3163 |
|
MD5 | c7323a9babdf36697c58df6735df51d8 |
|
BLAKE2b-256 | bedb00f88301a732f4f197b6d5fdabae1ebbf99802f40b88d3973418473dcb29 |