One of the core concepts of Boltflow is ease of use when it comes to working with a project, moving it to another working environment, and updating the used components.
In order to do this, we're going to use a simple shell script, that does a few things:
- Do a
git pullto make sure you're current with upstream.
- Creates the cache folders, if they're not present.
- Changes the file rights on the template folders, cache folders, etc.
- Fetch all required composer packages.
- Installs all required bolt extensions.
To run it, simply issue the command below:
If you're working on a project in a team, you might be working in your own
branch, or you might not. Running
boltflow at the start of a work session ensures that you're getting the same state of the projects as your co-workers. Or, the same state that you have in another location.
If you're getting an error about
composer.lock having outdated constraints, you should fix this by running an update (see below) and making sure both
composer.lock get committed to git.
To update the current version of Bolt to the latest stable version, run the following:
This will fetch the latest versions of Bolt and dependent composer packages,
for your development environment. You can test if everything works as expected.
If so, propagate the change into git by committing the updated
git add composer.lock extensions/composer.lock git commit -m "Updating Bolt, Bolt extensions and Composer packages." git push
If the change breaks your project, you can revert to the last known stable situation, like this:
git checkout -- composer.lock git checkout -- extensions/composer.lock ./boltflow.sh
This will revert the two
.lock files to the version in git, and it will run
the 'install' process to fetch the dependencies to match the previous state.