Great, one question, once n8n update a new version, how do u update on the instance you deployed? and also how not to lose data, workflows when you update the version?
@IvySaskia docker pull n8nio/n8n - This will pull the latest image. docker compose stop - Run this on the same n8n docker compose file. This will stop the container but should retain the volumes. docker compose up -d - Run this again to relaunch the container with the new image. It should remap the same volumes. Let me know if this helps... I have to put my kids to bed so I may not be back tonight. Feel free to shoot me an email if you need any additional help. steve@stevestechstuff.net
Really useful video. Thanks a lot.
hello I had some ideas but I don't know if these are feasible, could you tell me?
hello could you explain certain things to me I have a lot of difficulty understanding
Great, one question, once n8n update a new version, how do u update on the instance you deployed? and also how not to lose data, workflows when you update the version?
Mount the same volumes/paths when updating.
@@StevesTechStuff when I update to the new version the data, workflows, account is lost..thats why I ama asking how to do it correctly
@IvySaskia
docker pull n8nio/n8n - This will pull the latest image.
docker compose stop - Run this on the same n8n docker compose file. This will stop the container but should retain the volumes.
docker compose up -d - Run this again to relaunch the container with the new image. It should remap the same volumes.
Let me know if this helps... I have to put my kids to bed so I may not be back tonight.
Feel free to shoot me an email if you need any additional help.
steve@stevestechstuff.net