Version Update

To update from an older to a newer version or Lowcoder, please follow this guide:

Please always make a Backup / Copy of your /lowcoder-stacks folder.

The magic behind an easy update is to make use of the /lowcoder-stacks mounted folder in the docker installations. That enables you to change the Versions of Lowcoder but not touch the Application Data. Especially in the development of the platform itself, we follow this approach, and it saves us a lot of headaches and time. In the mounted /lowcoder-stacks folder, especially in the all-in-one Docker image installation, all application data and logs are stored. In other words, the Lowcoder MongoDB stores the Application Data of all your workspaces and Apps there, enabling you to exchange the docker without needing further backup and restore actions.

1) stop your Lowcoder:

With Docker Compose

docker-compose down

With pure Docker

docker stop [container-id]

Or in Docker Desktop

Stop and delete the "Container" you did run based on the old version.

If you did follow the /lowcoder-stacks folder mounting, no data would be lost.

2) create a backup copy of the lowcoder-stacks folder

Even if it should be never a problem, still we ask you kindly always to make a copy of the whole folder. Sometimes we have no other channce than to introduce breaking changes and we want to make sure you will never loss any data.

3) Download the latest docker files.

With Docker Compose

download docker-compose.yaml or docker-compose-multi.yaml file depending on which installation you prefer (all-in-one or multi-images)

With pure Docker

If you use Docker Desktop, you can simply pull the /latest tag or a specific version tag.

4) Run the new image

After the image is pulled, you can run the image (create a new container) and configure directly the Ports as well as the ENV Variables.

Mind to re-connect (mount) the /lowcoder-stacks folder

On pure Docker / Docker Desktop

With Docker Compose

docker-compose up -d

Multi Image Docker Version handling

Technically, the Docker Versions and releases go "Hand in Hand". That means that you should always operate the same backend version of API-Service-Image & Node-Service-Image as the Frontend-Image. However, in special situations, the separation of these concerns into different images gives you a degree of freedom to update only one of the images and check the compatibility.

Last updated


© Lowcoder Software LTD