Instance Management
Checkpoint version and upgrades
When you upgrade manually, you must upgrade to the checkpoint version released between your version and the latest version.
Appsmith checkpoint versions:
- v1.9.2
Access your Appsmith instance and make the following change to the docker-compose.yml file:
- Community Edition
- Business Edition
services:
appsmith:
image: index.docker.io/appsmith/appsmith-ce
container_name: appsmith
To:
services:
appsmith:
image: index.docker.io/appsmith/appsmith-ce:v1.9.2
container_name: appsmith
services:
appsmith:
image: index.docker.io/appsmith/appsmith-ee
container_name: appsmith
To:
services:
appsmith:
image: index.docker.io/appsmith/appsmith-ee:v1.9.2
container_name: appsmith
Save this file, then run the following command on your shell to restart Appsmith.
docker-compose up -d
With this, your server starts with the older version that makes all the necessary schema changes to your Appsmith instance. Once this process has been completed successfully (you can verify this by logging in to your Appsmith instance), you can return to the original version of your docker-compose.yml
file and resume normal operations.
- Community Edition
- Business Edition
services:
appsmith:
image: index.docker.io/appsmith/appsmith-ce
container_name: appsmith
services:
appsmith:
image: index.docker.io/appsmith/appsmith-ee
container_name: appsmith
Run the restart command once again:
docker-compose up -d
If you haven't been using your Appsmith instance for a while, it could be possible that there might be multiple versions that show up in the error message. In such a case, perform the same steps for each version in order, starting from the oldest.
Switching off auto updates
In your docker-compose.yml
file, the auto_update
container is responsible for periodically checking for updates to Appsmith and applying those updates. If you wish to disable this auto updating, please run the following command:
docker-compose rm -s -v -f auto_update
This brings down the auto_update
container, and update checks are no-longer performed. Note that however, if you run docker-compose up -d
later, for any reason, then this auto_update
will be brought up again. You can use that to turn auto updates on again in the future.
To check if auto updates are turned on in your instance, please run docker-compose ps
and see if there a server called auto_update
listed in the output, and if it's status is Up
. If not, then auto updates are turned off for your instance.