Git and concrete5 (empty directories at root location)
Permalink 1 user found helpful
Hi, I'd like to use Git to control versioning of a C5 website.
Since I need to apply a workaround for empty directories to be included in Git control, I'd like to know if the empty directories at the root location of a C5 site are necessary? I mean the ones that are made to override core files. e.g. [root]/controllers/ [root]/elements/ [root]/helpers/ etc.
Is the existence of those empty directories a must for a proper functioning of a C5 site, without any warnings/errors logged? Or are they there just as a courtesy for the future overrides? in which case, can I delete/ignore them safely?
Since I need to apply a workaround for empty directories to be included in Git control, I'd like to know if the empty directories at the root location of a C5 site are necessary? I mean the ones that are made to override core files. e.g. [root]/controllers/ [root]/elements/ [root]/helpers/ etc.
Is the existence of those empty directories a must for a proper functioning of a C5 site, without any warnings/errors logged? Or are they there just as a courtesy for the future overrides? in which case, can I delete/ignore them safely?
Could you start from the Concrete5 project on Github and create a repo from that. Mine has .gitignore files throughout which I guess is what you'd need to include the empty directories in Git Control?
Try using find . -type d | xargs ...... To create a blank file in subdirs.
We find it useful to have the directories there
We find it useful to have the directories there
