Hello,
[thread updated – original post is below]
Themes are most frequently taken from existing ones, hosted on Github for instance. For our static sites, this lead to a git tree inside our files. We also often manage our posts & full static sites with Git. A consequence is that there is several git trees packed together.
What is the solution you find to manage them?
- Putting all the
git clone
andgit pull
inside aREADME.md
file? - Creating a shell script to execute commands like
mkdir -p themes/blahblah && cd themes/blahblah/ && git pull
? - Making a git subtree (seems tricky)?
- Making a git submodule (seems evil)?
Thanks for the ideas!
[original post]
My site tree is managed via a git repository. I have installed external themes and I would like to be as sustainable as possible. What would you advise me to manage the themes’ git trees? I need to be able to rebuild a website from scratch if (for instance) my main computer would crash.
I can imagine:
- Putting what to do inside a
README.md
file (all thegit clone
and so on) - Creating a shell script to execute commands like
mkdir -p themes/blahblah && cd themes/blahblah/ && git pull
or things like this. - Making a git subtree (seems tricky)
- Making a git submodule (seems evil)
Actually for existing projects I used to put all that in a README file. For deployments I sometimes create a shell script (which is the case for instance for my mathematics site).
Thank you for your advice.