From the docker file, I don’t see that you have configured the separate DB instance. So when you updated the image and replaced the container (run a new one), everything, that was there, now gone.
For the persistent configuration, you have to use the external database and an attachable volume (that is already attached according to the configuration)
Hi @barn4k, thanks for the response. I had a single (but a bit long) workflow that I lost. I abandoned the hope of recovery even before your message and recreated that. Will be testing the workflow.
That being said, with the setup I have, how will I retain data for future upgrades?
I have set up a workflow that backs up all workflows to Gitub and will do manual backups before upgrades as well. What about credentials? Do I have to set those up after every upgrade?
I, personally, would not recommend backup credentials to the GitHub due to security reasons. Even the encrypted creds may be exposed if you aren’t accurate and store somewhere the encryption key. If you don’t have many workflows/creds, the easiest thing is to create manual backups or a backup workflow that will store the data on the attachable volume (e.g. /home/node/.n8n or /files)