Document Actions
Developing, Staging, Syncing
Working in one location and syncing that work to another location is critical if you want to be an efficient Plone developer. Here are some tips.
Based on the talk given by Joel Burton at the Plone Conference in Vienna, this Tutorial discusses some of the best practices for Plone development. If you are doing site development with Plone and want to keep your sanity, this is a must-read. Requires some familiarity with Zope and Plone.
Page
7
of
9.
Developing, Staging, Syncing
- Working off laptop and moving to server
- Moving from staging server to production server
- Working in teams
You Have a Laptop: Use It
- It's not a $3000 ssh client
- Faster edit/test/debug cycle.
- No wires, no wireless
- Easier to work privately
Subversion for Sharing
- Work on your laptop
- When at the "right point", check-in your code
rsyncto your sandbox on server- Emergency changes on server can be handled, too
Simple Sandboxes
- Each developer gets a skin folder in your product
- rsync your skin changes to your skin folder
- Each developer has their own skinpath, with their skinfolder as most customized
- Developers can switch from their sandbox skinpath to common skinpath.
Synchronizing of Content
- Create starter content in setup scripts
- Create starter content in
.zexpfiles- Can't change, though
- Use
ZSyncerto sync from one server to another - Use AT
XMLToolorMarshallto export/import XML of content
by
Joel Burton
—
last modified
December 10, 2005 - 21:43
All content is copyright Plone Foundation and the individual contributors.
