Best Practices of Plone Development
Best Practices of Plone Development
Best Practices of Plone Development
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
1.11 Developing With Others 1 BEST PRACTICES FOR PLONE DEVELOPMENT<br />
1.11 Developing With Others<br />
1.11.1 You Have a Laptop: Use It<br />
• It’s not a $2000 ssh client<br />
• Faster edit/test/debug cycle.<br />
• No wires, no wireless<br />
• Easier to work privately<br />
1.11.2 Subversion for Sharing<br />
• Work on your laptop<br />
• When at the “right point”, check-in your code<br />
• ’rsync’ to your sandbox on server<br />
• Emergency changes on server can be handled, too<br />
1.11.3 Simple Sandboxes<br />
• Each developer gets a skin folder in your product<br />
• rsync your skin changes to your skin folder<br />
• Each developer has their own skinpath, with their skinfolder as most customized<br />
• Developers can switch from their sandbox skinpath to common skinpath.<br />
53
Change language