Now that Kirby’s command-line interface has been out for a little while, we have at least three ways to install Kirby and keep it up-to-date. So I’m wondering, how do you keep your Kirby projects up-to-date and all the plugins/fields that come with it? What’s your approach to version control?
The Kirby CLI
Downloading the latest ZIP file and manually copying the new files
Some other method?
One thing I love about Kirby is the diversity of the community and the fact that there is often more than one “right” way to do things.
I also use git submodules, although I tend to run into trouble with them from time to time . The good thing about using submodules is that it gives us the possibility to easily checkout developer branches. That’s missing from the cli, unfortunately.
I do use the cli to quickly install test versions of the starterkit or compatible plugins though, but not for my projects. I don’t like moving files and folder around, though …
I used submodules so far but I really like the CLI and it works quite well. So this is the way I want to go in the future. I’m still doing a lot of Drupal stuff and I’m used to use drush, which is Drupals’ super powerful CLI.
I like this way of working. Once you’ve started using the command line you don’t wanna miss it …
I use Composer to install Kirby and some plugins. It’s rather verbose, but the end result is a config file you can version and run with composer install to get the same exact install, so it’s still worthwhile.
So I have this in my .gitignore:
# Ignore stuff installed with Composer
# (e.g. folders but not scripts in plugins dir)