/.idea /vendor/ /cache/ !/cache/.gitkeep /images/ !/images/.gitkeep /tmp/ !/tmp/.gitkeep /assets/ !/assets/.gitkeep /backup/ !/backup/.gitkeep /logs/ !/logs/.gitkeep
Here’s what I had in one of the last projects I worked on:
.sass-cache bower_components *.css.map cache/** logs/** .DS_Store assets/** backup/** config.codekit
That’s my .gitignore I use for my projects.
# Sass .sass-cache *.map # Add the entire Grav site to GitHub # https://getgrav.org/blog/developing-with-github-part-2 composer.lock backup/* !backup/.* cache/* !cache/.* assets/* !assets/.* logs/* !logs/.* images/* !images/.* user/data/* !user/data/.* user/accounts/* !user/accounts/.* # local cofig and security user/localhost/config/security.yaml user/config/security.yaml user/config/site.yaml user/config/system.yaml user/config/plugins/email.yaml #specific .htaccess -> dists in webserver-congifs .htaccess tests/_output/* tests/_support/_generated/* tests/cache/* tests/error.log # OS Generated .DS_Store* ehthumbs.db Icon? Thumbs.db *.swp ### Node ### npm-debug.log # Runtime data pids *.pid *.seed *.pid.lock # nyc test coverage .nyc_output # node-waf configuration .lock-wscript # Dependency directories node_modules jspm_packages # Optional npm cache directory .npm # Optional eslint cache .eslintcache # Optional REPL history .node_repl_history .idea/hammes.iml .idea/modules.xml .idea/workspace.xml .idea/dictionaries/Sebastian.xml .idea/inspectionProfiles/Project_Default.xml
did one of you worked with gantry???
Since I am a bit new with the flat cms systems I didnt really have a good solution yet for the fact that constant changes of content (by client) always totally messes up my git. How do you handle that issue? Was even considering to put the “pages” folder into the gitignore…
Tricky question - I suppose it comes down what your main focus in developing is within Grav. E.g. I am mostly focused to develop within the theme folder (and all assets within) as such I .gitignore /pages /plugins /data as they ar enot relevant for the theme dev process. If you need then to get your system up to date with content and plugins you can always take a snapshot from remote (or staging).