How to upgrade version 1.5 to 1.6?
Download and install 1.6 and then update the database with
flectra-bin -d <dbname> -u all --stop-after-init
When flectra has finished the migration it will be stopped directly. Now you can use your database with flectra 1.6
Don’t forget to make a backup first!
dbname is the name of the database created in Flectra?
If I have several such bases?
Jup dbname is the name of the database you see in database manager .
Just use the name as -u dbname, like -u FlectraDemo
On an similar theme… How long does it take for the docker image to be updated?
Using default tag: latest latest: Pulling from flectrahq/flectra Digest: sha256:ff161ce36dc6357ff52bc4317463a28a7292d21fabbc15991932c3fa1bf78b32 Status: Image is up to date for flectrahq/flectra:latest
The latest pull as of today is still v1.5.
[email protected]:/# dpkg-query -s flectra Package: flectra Status: install ok installed Priority: optional Section: net Installed-Size: 506917 Maintainer: FlectraHQ <[email protected]> Architecture: all Version: 1.5.20190302
That is 2 months old now and 1.6 was released 2019-03-28
as i know the docker image is now on 1.6.
have you checked again?
For reference. Yes. Docker images is now 1.6. However though it all seems to work I am noticing these warnings in the logs.
flectra.addons.base.ir.ir_cron: Skipping database mycompany as its base version is not 188.8.131.52.
Is the image supposed to upgrade the DB schema itself or do you need to do that manually ?
normally with -u all the db will be updated…
im not the docker specialist, cause i mostly work with the source code…
Hmm so can I do -u from the command line inside the container when a copy of flectra is already running?
This will be one solution - but not the best one.
It is better to run the same image from your host (not in the container) with the -u command:
docker run -ti --rm <imagename> -d <dbname> -u all --stop-after-init
Like this a new container is built which will process the upgrade and it will be stopped when the upgrade is done (–stop-after-init). The parameter --rm will directly remove the container when the upgrade is finished.
It is possible that you need more command args (e.g. -c to set the path to config file).