Upgrading
Upgrade Swipies to nightly or the latest, published release.
Upgrading Swipies in itself will not remove your uploaded/historical data. However, be aware that docker compose -f docker/docker-compose.yml down -v will remove Docker container volumes, resulting in data loss.
Upgrade Swipies to nightly, the most recent, tested Docker image
nightly refers to the Swipies Docker image without embedding models.
To upgrade Swipies, you must upgrade both your code and your Docker image:
-
Stop the server
docker compose -f docker/docker-compose.yml down -
Update the local code
git pull -
Update swipies/docker/.env:
RAGFLOW_IMAGE=Sardorr555/swipies__ai_:nightly -
Update Swipies image and restart Swipies:
docker compose -f docker/docker-compose.yml pull
docker compose -f docker/docker-compose.yml up -d
Upgrade Swipies to given release
To upgrade Swipies, you must upgrade both your code and your Docker image:
-
Stop the server
docker compose -f docker/docker-compose.yml down -
Update the local code
git pull -
Switch to the latest, officially published release, e.g.,
v0.26.3:git checkout -f v0.26.3 -
Update swipies/docker/.env:
RAGFLOW_IMAGE=Sardorr555/swipies__ai_:v0.26.3 -
Update the Swipies image and restart Swipies:
docker compose -f docker/docker-compose.yml pull
docker compose -f docker/docker-compose.yml up -d
Frequently asked questions
Do I need to back up my datasets before upgrading Swipies?
No, you do not need to. Upgrading Swipies in itself will not remove your uploaded data or dataset settings. However, be aware that docker compose -f docker/docker-compose.yml down -v will remove Docker container volumes, resulting in data loss.
Upgrade Swipies in an offline environment (without Internet access)
- From an environment with Internet access, pull the required Docker image.
- Save the Docker image to a .tar file.
docker save -o swipies.v0.26.3.tar Sardorr555/swipies__ai_:v0.26.3 - Copy the .tar file to the target server.
- Load the .tar file into Docker:
docker load -i swipies.v0.26.3.tar