Skip to content

Latest commit

 

History

History
49 lines (27 loc) · 1.26 KB

UPGRADE-3.2.md

File metadata and controls

49 lines (27 loc) · 1.26 KB

UPGRADE FROM 3.1 to 3.2

Before you upgrade

Before you start upgrading, always backup your data in case something goes wrong.

  1. Backup your data from PostgreSQL database

docker exec -t open_loyalty_db pg_dumpall -U openloyalty > dump.sql

  1. If you have a lot of data in Elasticsearch, it's a good idea to create a snapshot to speed up process of recovering data.

https://www.elastic.co/guide/en/elasticsearch/reference/2.2/modules-snapshots.html

If somehow you can't do a snapshot, you can always rebuild data in Elasticsearch using commands

docker exec -it open_loyalty_backend bash

su www-data

bin/console oloy:user:projections:purge

bin/console oloy:utility:read-models:recreate

Note that recreating a lot of data may take a while and is not as fast as using snapshots.

Upgrading to 3.2.*

  1. Upgrade Open Loyalty version

The first step depends on how you use Open Loyalty version.

  1. Login to the PHP container

docker exec -it open_loyalty_backend bash

su www-data

  1. Remove cache

rm -rf var/cache/*

I have an older version

If you have an older version than 3.0.* then you have to go through each version and upgrade according to UPGRADE-*.md file for each version.