Keep your project up-to-date

For security and functionality reasons you should keep your project updated with latest version. Naviga maintain the version in StarterKit. Here's what you need to maintain in your project.

Update to latest WordPress patch version

Step 1: Test the new version locally

./bin/wordpress-install.sh -v 5.8.0

./bin/wordpress-install.sh -v 5.8.*

Step 2: Set the version you tested in bin/init.sh.

./bin/init.sh

##
 # The version can contain wildcard:
 #+ 1.2.3 - Will fetch the exact version
 #+ 1.2.* - Will fetch the latest patch on version
 #+ 1.* - Will fetch the latest minor on version
 #
WORDPRESS_VERSION="5.8.3"

This version will be used on server deploys.

Other developers will automatically get the version when running.

Step 3: Install the Wordpress version you specified.

make init  # Choose to reinstall WordPress when prompted

Update to latest PHP patch version

Step 1: Find latest patch version for .

Step 2:

Set version for local development in ./docker-compose-local.yml.

Set version for AWS server hosting in ./docker-compose.yml.

Example docker-compose.yml

php-fpm:
    image: infomakerscandinaviaab/php-fpm:7.4.24

Naviga Web packages and StarterKit are continuously updated with PHP versions.

Update Composer dependencies

Step 1: Update to latest package versions based on constraints in ./composer.json.

# Check what packages can be updated (optional)
composer outdated

# Run with composer through Docker container (preferred)
make composer update

# Or run with locally installed composer
composer update

Step 2: Test and verify the new package versions.

Step 3: Commit composer.lock to save versions into your project.

Update Node dependencies

Step 1: Check what is old and could be updated.

npm outdated

Step 2: Update the packages you want manually.

npm install <package name>@<version>

Step 3: Commit package.json and package-lock.json to save versions into your project.

PreviousDebugging NextGulp and Sass

Last updated 2 years ago

Was this helpful?