Site Development Processes for Small Teams
•
2 likes•1,340 views
This document outlines a process for small teams to develop TYPO3 sites. It recommends creating a base package with common configurations and files to standardize site builds. Sites should be version controlled with code and configurations in Git and content outside of it. Local development involves setting up sites from version control in MAMP. Deployment is done with Capistrano to automate pushing changes to multiple servers, and staging/testing helps avoid issues. The process aims to streamline site builds for consistent results across a distributed team.
More Related Content
What's hot
What's hot (20)
Similar to Site Development Processes for Small Teams
Similar to Site Development Processes for Small Teams (20)
Recently uploaded
Recently uploaded (20)
Site Development Processes for Small Teams
- 1. Site Development Process for Small Teams BUSY NOGGIN DIGITAL serious websites for those who mean business
- 2. What We Learned from Goldilocks and the Three Bears BUSY NOGGIN DIGITAL serious websites for those who mean business
- 4. BUSY NOGGIN DIGITAL (1) Project Manager / Creative Director / Site Integrator / Frontend Developer (1) PHP Developer (2) Designer / Frontend Dev / Site Integrator The Small Team • Wide range of TYPO3 experience, ranging from <1 year to 10 years • Semi-virtual team, separated by 8,000 miles
- 5. BUSY NOGGIN DIGITAL Why do we need a process?
- 7. BUSY NOGGIN DIGITAL Kickstarting a Site Download TYPO3 Source Copy/Paste BuildYour Own CMS! Create a Base Package
- 8. BUSY NOGGIN DIGITAL Create A Base Package TYPO3 Source Extensions Extension Config Extension Templates Default Site Config Wireframe Template Backend Permissions What steps do you perform as part of every site build?
- 9. BUSY NOGGIN DIGITAL Create A Base Package TYPO3 Source Extensions Extension Config Extension Templates Default Site Config Wireframe Template Backend Permissions Custom Extensions Custom TemplateSite Configuration Make Use of Inheritance for Individual Sites
- 10. BUSY NOGGIN DIGITAL Create A Base Package Consistent, modular structure for extensions, skins, etc tt_news Configuration TypoScript Resources Private SASS Templates Public Images JavaScript StyleSheets my_skin Configuration TypoScript Resources Private SASS Templates Public Images JavaScript StyleSheets
- 15. BUSY NOGGIN DIGITAL Version Control I think the hosting company does backups Let’s put the content in Git! Everything is a submodule! Code & Configuration in Git Content outside Git
- 16. BUSY NOGGIN DIGITAL • ... for the same reasons you would version control an extension • Change tracking and rollback • Keep code in sync with other team members • Easy TYPO3 upgrades by updating submodule Version Control Why should I version control a site?
- 17. BUSY NOGGIN DIGITAL • Any content generated in production - Database - Static files in fileadmin - Static files in uploads - Anything in typo3temp - Temp files and logs in typo3conf - Autogenerated RealURL configuration - Server-specific configuration (ie. localconf.site.php) Version Control What should I leave out of version control?
- 19. BUSY NOGGIN DIGITAL Local Development Everyone just starts from the same place Virtual machine per site MAMP +Version Control
- 20. BUSY NOGGIN DIGITAL • Most projects are basic LAMP stack • Run (L/M/W)AMP locally for simplicity • Develop inside a feature branch or general development branch • Tower and SourceTree make GIT more approachable • MAMP Pro makes Apache & Virtual Hosts more accessible Local Development Basic Setup
- 21. BUSY NOGGIN DIGITAL • Checkout Git repository • Set up in MAMP • Sync database and content via Syncing Secret Sauce (stay tuned until the end of the presentation) Local Development Usage
- 23. BUSY NOGGIN DIGITAL Deployment FTP or Edit on Production DevOps for Entire Server Deploy Site to Multiple Targets
- 24. BUSY NOGGIN DIGITAL • Remote multi-server automation tool • Run commands locally, execute them on the server • Multi-stage (testing, production) and Muti-role (web, db) • Common Tasks - cap [stage] deploy:setup - cap [stage] deploy:pending - cap [stage] deploy - cap [stage] deploy:rollback Deployment Capistrano Basics
- 25. BUSY NOGGIN DIGITAL Deployment Capistrano Deployment Structure my_site current -> releases/20130530161342 releases 20130530161342 config site typo3_src 20130406124812 config site typo3_src shared cached-copy
- 26. BUSY NOGGIN DIGITAL Deployment TYPO3-flavored Capistrano my_site current -> releases/20130530161342 releases 20130530161342 20130406124812 shared cached-copy config localconf.site.php site fileadmin typo3temp uploads
- 27. BUSY NOGGIN DIGITAL • Capistrano tasks for TYPO3 CLI Interface • Trigger Solr re-index • Clear Cache • Update Database • EXT:coreapi Deployment TYPO3-flavored Capistrano
- 28. BUSY NOGGIN DIGITAL Deployment See also: TYPO3 Surf (one room over)
- 29. BUSY NOGGIN DIGITAL Staging & Testing
- 30. BUSY NOGGIN DIGITAL Staging & Testing “Works on my machine” Content Staging Continuous Integration Internal Test Server
- 31. BUSY NOGGIN DIGITAL Staging & Testing
- 32. BUSY NOGGIN DIGITAL Staging & Testing
- 33. BUSY NOGGIN DIGITAL Syncing Secret Sauce
- 35. BUSY NOGGIN DIGITAL > cap sync:files > cap sync:database > cap production sync:files > cap production sync:database
- 37. BUSY NOGGIN DIGITAL • Vagrant for sites with needs outside LAMP stack • Define normal site building stages and deliverables produced • Checklists for guiding a site build through common tasks • Documentation for deployment, version control, etc Next Steps It’s too big right now, but where are we headed?
- 38. BUSY NOGGIN DIGITAL Tools of the Trade
- 39. BUSY NOGGIN DIGITAL Tools of The Trade
- 43. BUSY NOGGIN DIGITAL serious websites for those who mean business