Skip to content

Instantly share code, notes, and snippets.

@wsakaren
Last active June 3, 2016 05:36
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 1 You must be signed in to fork a gist
  • Save wsakaren/5b1a2cde5ac8d33f12fa to your computer and use it in GitHub Desktop.
Save wsakaren/5b1a2cde5ac8d33f12fa to your computer and use it in GitHub Desktop.
Magento2 Major Directories
Ignoring frontend logic the important directories I can see so far are:
- app/code/Magento - Holds Magento implementation modules, e.g Customer, Cart, Checkout
- internal/Magento/Framework - Magento Framework e.g. Session Handling, SQL Setup, Cache
- pub/errors - Can move the local.xml.sample to local.xml so you don't have to keep looking in report directory!!
- vendor - 3rd Party libraries loaded via composer
- app/<module_vendor> - 3rd Party magento extensions
- app/etc/env.php - db credentials, replaces local.xml?
- var/cache, var/generation & var/page_cache - Delete these 3 directories to fully flush cache
- dev/tests - Unit Tests
To create a module start off by just adding it under app/code/<Vendor>/<Extn>. You can move it to composer later (it should live in vendor/<Vendor>/<Extn>
@wojtekn
Copy link

wojtekn commented Jan 11, 2015

Karen, you may also add var/generation to the list of directories needed to flush cache.

@wsakaren
Copy link
Author

Added, thanks ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment