Understand the Structure of CodeIgniter
Posted on 29. Aug, 2009 by Shawn McCool in PHP, Screencasts, Web Development
In this screencast I attempt to explain the structure and terminology of the Code Igniter MVC PHP development framework.
Related Posts
- Developing a Website with CodeIgniter Part 1: Development Environment and Framework Configuration
- CodeIgniter at the Nashville PHP meetup March 20th.
- Developing a Website with CodeIgniter Part 4: Admin Site CRUD
- Why Should I Use CodeIgniter?
- How to Write a Better Model in CodeIgniter
Share this Post
Show Your Appreciation
If you'd like to express your appreciation for the work I've done why not buy me a coffee?Click here to donate $3 to my caffeine fund.
Thanks for the video it was very informative. Before watching the video, I did some googling on MVC and downloaded the codeIgnitor framework but it wasn’t clear. After watching the video it all clicks. Cheers.
Thanks for the feedback, Andrew. I’m interested in any specific challenges that you face as a developer who is new to Code Igniter. Is there anything that took a while to really “click” for you or any topics for screencasts / tutorials that new CI developers could benefit from?
Shawn,
Since you are soliciting suggestions for tutorials/ screencasts, I’d like to suggest a quick tutorial on where to actually place images and css files that are used and reused on a site. I’ve been looking around online and everyone seems to have a different suggestion. I downloaded and looked at Derek Allard’s BambooInvoice and he seems to put a css folder and an images folder at the same level as the system folder and then just link to them in the views using href=css/ or href=image/. To me that seems to separate elements of the view from the view folder but I’m just a beginner. What would you suggest?
By the way I’m looking forward to part 4!
Kris
Great idea for a post! I do have some strong feelings on this subject. Not necessarily with the location itself, but with ensuring flexibility over the lifespan of a website.
http://shawnmccool.com/2009/11/23/managing-assets-with-codeigniter/
As a note about placement:
Many people would move the CodeIgniter structure out of the web root folder, and only leave the .htaccess, index.php and assets folders. index.php can be configured to access CodeIgniter from another folder, further securing your site from the kinds of server misconfiguration that can leave your valuable data exposed.