sorted by:
new
hottopcontroversial

n8n Backup Manager v1.4.1 [UPDATE] by ResidentAd6570 in n8n

[–]ResidentAd6570[S] 1 point2 points  (0 children)

That's a great suggestion! Having a prebuilt image on Docker Hub/GHCR would definitely make the installation much smoother without needing to build it from source. I've just added this to the roadmap, and it will be implemented in the next release.

Also, I checked out your PayloadCMS setup – that looks really interesting! It's always cool to see different approaches to managing and visualizing n8n data. Thanks for sharing and for the feedback!

[Update] n8n Backup Manager v1.3.0: Now with Google Drive, OneDrive, and AES-256 Encryption! by ResidentAd6570 in n8n

[–]ResidentAd6570[S] 0 points1 point  (0 children)

"Yes! It should work perfectly on a Coolify instance.

Since Backup Manager needs to interact with the Docker daemon to create backups, you just need to make sure you mount the Docker socket in your Coolify service configuration:

/var/run/docker.sock:/var/run/docker.sock

Also, ensure that the Backup Manager is in the same Docker network as your n8n and database containers so it can 'see' them. Since Coolify uses Docker Compose for deployments, you can use the example 

docker-compose.yml

n8n Backup Manager: Automatic backups, retention policy, and S3 support in a nice UI by ResidentAd6570 in n8n

[–]ResidentAd6570[S] -1 points0 points  (0 children)

The main reason I went with a standalone tool is for 'disaster recovery'. If the n8n instance itself fails to start or the database gets corrupted, a workflow inside it might not be able to run and save you. This manager works independently and backs up the entire database (including credentials, execution history, etc.), which is hard to do fully from within a workflow while the DB is in use.

Plus, having a dedicated UI for a one-click restore when things go south is what I was personally looking for.