Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
craftcms .gitignore
# Craft runtime and backups folders
# ----------------------------------------------------------------------
craft/storage/runtime/*
craft/storage/backups/*
# Uploaded files
# ----------------------------------------------------------------------
public/assets/uploads/*
# Misc files
# ----------------------------------------------------------------------
.DS_Store
Thumbs.db
.cache
.project
.settings
.tmproj
*.esproj
nbproject
*.sublime-workspace
*.sublime-project
*.komodoproject
.komodotools
_notes
dwsync.xml
logs/*
@aaronbushnell

This comment has been minimized.

Copy link

aaronbushnell commented Mar 26, 2013

I like to include these things because they encapsulate most OS/editor/file system junk:

# Numerous always-ignore extensions
*.diff
*.err
*.orig
*.log
*.rej
*.swo
*.swp
*.vi
*~
*.sass-cache

# OS or Editor folders
.DS_Store
Thumbs.db
.cache
.project
.settings
.tmproj
*.esproj
nbproject
*.sublime-project
*.sublime-workspace
*.komodoproject
.komodotools
_notes
dwsync.xml
@aaronbushnell

This comment has been minimized.

Copy link

aaronbushnell commented Mar 26, 2013

Out of curiosity though, why would you want to ignore the .gitignore file? Couldn't someone then clone the repo (without the .gitignore) and be able to commit a .DS_Store file to it? I've never done this so I'm just wondering.

@BenParizek

This comment has been minimized.

Copy link

BenParizek commented Mar 29, 2013

I think you may be able to ignore the entire runtime folder.

craft/storage/runtime/*

I've also added the backups folder as we keep backups elsewhere so no real need to have them in the repo too:

craft/storage/backups/*

@jeromecoupe

This comment has been minimized.

Copy link
Owner Author

jeromecoupe commented Sep 17, 2013

Thanks guys! Updated

@aaron: I keep .gitignore out because it is a git-specific file and, as such, I see it as not belonging in the repo itself (everybody has its own copy). That being said, now that I think about it after your comment, it makes sense to keep it in when working teams.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.