Upgrading from v0.16.0 to v0.17.0 is fairly straightforward, and only requires running postgres migrations. This guide will walk you through the process of upgrading your Dittofeed instance.
docker-compose.lite.yaml
FileFirst, add the environment variable BOOTSTRAP: "false"
to your docker-compose.lite.yaml
file, if it isn’t set already. This will prevent your lite instance from running bootstrap operations when it restarts.
Next, make sure you have an admin-cli
instance specified in our docker-compose.lite.yaml
file. We’ll be using this service to run our migrations.
Your docker-compose.lite.yaml
file should look something like this:
admin-cli
ServiceNext, run the following command to start your admin-cli
service:
Run Dittofeed’s database migrations before deploying the new version of Dittofeed:
docker-compose.lite.yaml
FileUpgrade the version in your docker-compose.lite.yaml file to v0.17.0:
Now restart your lite instance:
admin-cli
ServiceFinally, stop the admin-cli
service:
values.yaml
FileFirst, add the environment variable BOOTSTRAP: "false"
to your values.yaml
file for the dittofeed helm chart, if it isn’t set already. This will prevent your lite instance from running bootstrap operations when it restarts.
dittofeed-admin-cli
ChartNext, run the following command to install the dittofeed-admin-cli
chart:
Make sure that the dittofeed-admin-cli
pod is running the version of the dittofeed-admin-cli
chart that you’re upgrading to.
Or set the tag
in your values.yaml
file to v0.17.0
:
Run Dittofeed’s database migrations before deploying the new version of Dittofeed:
Exec into the dittofeed-admin-cli
pod:
Run the migrations:
Update the tag
in your values.yaml
file to v0.17.0
:
Upgrade the dittofeed chart:
dittofeed-admin-cli
Helm ChartFinally, uninstall the dittofeed-admin-cli
deployment:
Upgrading from v0.16.0 to v0.17.0 is fairly straightforward, and only requires running postgres migrations. This guide will walk you through the process of upgrading your Dittofeed instance.
docker-compose.lite.yaml
FileFirst, add the environment variable BOOTSTRAP: "false"
to your docker-compose.lite.yaml
file, if it isn’t set already. This will prevent your lite instance from running bootstrap operations when it restarts.
Next, make sure you have an admin-cli
instance specified in our docker-compose.lite.yaml
file. We’ll be using this service to run our migrations.
Your docker-compose.lite.yaml
file should look something like this:
admin-cli
ServiceNext, run the following command to start your admin-cli
service:
Run Dittofeed’s database migrations before deploying the new version of Dittofeed:
docker-compose.lite.yaml
FileUpgrade the version in your docker-compose.lite.yaml file to v0.17.0:
Now restart your lite instance:
admin-cli
ServiceFinally, stop the admin-cli
service:
values.yaml
FileFirst, add the environment variable BOOTSTRAP: "false"
to your values.yaml
file for the dittofeed helm chart, if it isn’t set already. This will prevent your lite instance from running bootstrap operations when it restarts.
dittofeed-admin-cli
ChartNext, run the following command to install the dittofeed-admin-cli
chart:
Make sure that the dittofeed-admin-cli
pod is running the version of the dittofeed-admin-cli
chart that you’re upgrading to.
Or set the tag
in your values.yaml
file to v0.17.0
:
Run Dittofeed’s database migrations before deploying the new version of Dittofeed:
Exec into the dittofeed-admin-cli
pod:
Run the migrations:
Update the tag
in your values.yaml
file to v0.17.0
:
Upgrade the dittofeed chart:
dittofeed-admin-cli
Helm ChartFinally, uninstall the dittofeed-admin-cli
deployment: