Files to include with Git

[shogun]

What's your best process with process wire and git. What files do you include (and/or exclude) in git? to make sure you still have all your code backed up in git without having too much unnecessary inflation.

[wbmnfktr]

In most cases... everything but /wire/.

[wbmnfktr]

And of course... always a fresh DB dump.

[louisstephens]

I do the same as wbmnfktr. I also include a github action that auto ftp/pushes the updated files to a directory on my server that can be found here: https://github.com/SamKirkland/FTP-Deploy-Action

[shogun]

What about site/assets/sessions? Those seem to create permissions problems when moving to a server. Are these needed? or are these local to the current copy of the site.

[wbmnfktr]

29 minutes ago, louisstephens said:

I do the same as wbmnfktr. I also include a github action that auto ftp/pushes the updated files to a directory on my server that can be found here: https://github.com/SamKirkland/FTP-Deploy-Action

Woah... that sounds nice.

8 minutes ago, shogun said:

What about site/assets/sessions? Those seem to create permissions problems when moving to a server. Are these needed? or are these local to the current copy of the site.

You can safely ignore them if necessary. They never caused any issues within my setups and environments so I never bothered to ignore them.

 

[dragan]

Actually, the .gitignore in PW root is a nice starting point already. Some of the things I would probably add:

*.notes
*.sql
*.zip
site/assets/cache/*
site/assets/ProCache*
site/assets/pwpc/
site/assets/sessions/
wire/

.sql + .zip are most likely local backups, so I def. don't want them included

site/assets/... stuff depends - cache (regular + ProCache) stuff + sessions I'd also not want to carry over.

wire/ should certainly not be part of a repo.

btw: .notes is just how I store login details; Apache blocks web-access to any files starting with a dot anyway, but you don't want to take chances, so I added this to .gitignore too.