Successfully reported this slideshow.

VersionEEring

1

Share

Upcoming SlideShare
Introduction to git
Introduction to git
Loading in …3
×
1 of 28
1 of 28

VersionEEring

1

Share

Download to read offline

Why and how to use version control with an ExpressionEngine website. Version control is essential to good development practices, but setting it up with a database-driven website can be tricky.

Why and how to use version control with an ExpressionEngine website. Version control is essential to good development practices, but setting it up with a database-driven website can be tricky.

More Related Content

Related Books

Free with a 14 day trial from Scribd

See all

Related Audiobooks

Free with a 14 day trial from Scribd

See all

VersionEEring

  1. 1. VersionEEring Why and how to use version control with ExpressionEngine.
  2. 2. What is version control?
  3. 3. What is version control? A program that tracks changes to files and folders for you.
  4. 4. Also goes by these names. Source Control Manager (SCM) Revision Control System (RCS) Version Control System (VCS) That-Thing-That-Just-Saved-My-Ass
  5. 5. Different flavors? Yup. Each has its own way of tracking your changes. Here are a few: CVS - SVN - Git - Mercurial - Bazaar Darcs - Perforce - Fossil - BitKeeper http://en.wikipedia.org/wiki/List_of_revision_control_software
  6. 6. What kinds of files? Text! But also: Graphics Binary WHATEVER YOU WANT.
  7. 7. Why use version control?
  8. 8. Because this sucks.
  9. 9. Because this sucks.
  10. 10. Because this really, really sucks.
  11. 11. How to get started. No servers, nothing fancy - this is all local, baby. So no excuses.
  12. 12. 1. Pick a system. We’re going with Git.
  13. 13. 2. Install it on your computer. http://git-scm.com/download
  14. 14. 3. Set up a repository for your existing project. $  cd  ~/Sites/myproject Change to the project folder. $  git  init Initialize the repository. $  git  add  . Add everything in the project folder to the repository. $  git  commit  -­‐m  "Initial  commit." Make your first commit.
  15. 15. 4. Make some changes, and commit them. $  git  status Tell me what’s changed. (New file!) $  git  add  index.html Add the new file to the repository. $  git  status Tell me what’s changed. (Just making sure we didn’t miss anything.) $  git  commit  -­‐m  "Added  homepage." Commit the change.
  16. 16. 5. Rinse and repeat until you’re ready to share.
  17. 17. A Basic Workflow One way to use version control in practice, with actual live websites.
  18. 18. 1. Define your environments. Some popular ones: - Local - Development (overkill for team of one) - Staging (can be same as Development) - Live
  19. 19. Workflow show ‘n tell
  20. 20. Git and EE, sitting in a tree.
  21. 21. Gotcha #1: Paths. Let’s play with settings!
  22. 22. 1. Make all paths in the Control Panel relative. EE1: Admin > System Preferences > General Configuration EE2: Admin > General Configuration
  23. 23. Don’t forget uploaded files and generated images. EE1: Admin > System Preferences > Captcha Preferences (Each upload destination) Admin >Channel Administration > File Upload Preferences (Each channel) Admin > Channel Administration > Channel Management > Edit Channel Preferences EE2: Admin > Content Administration > File Upload Preferences
  24. 24. Gotcha #2: Environment variables. Let’s play with config files!
  25. 25. Gotcha #3: User-generated files. Keeping filesystems in sync.
  26. 26. Gotcha #4: Databases. Pick your poison.
  27. 27. Further Resources New to version control? Check out Version Control for Designers: http://hoth.entp.com/output/git_for_designers.html Not new to version control, but new to Git? Check out Git Reference: http://gitref.org/ More on the topic of Git and EE: http://gititon.masugadesign.com/ <-- A++ WOULD RECOMMEND http://j.mp/ee2multiserver

×