You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@regenrek Sorry for the late response - I didn't see or expect an open issue ticket. :) Currently, volumes are automatically attached to /mnt/hetznerxxxxx, and configuration needs to be done manually. How you use them is up to you. I plan to automate this task with Ansible. You can remove the volumes in your setup if the node storage is sufficient for your needs.
To be honest, I haven't used backup inside Coolify, but using an existing AWS bucket is a good choice... or you can self-host MinIO on a single-node K3s and deploy MinIO operator and tenant with Helm charts
Hey,
awesome repo!
I have a question. Why there are volumes exist in your setup. Are they being used by the apps or will be the ssd disk used of esch worker?
additionaly why does every worker has a volume since I dont think they are mirrored (like a raid).
im asking this because im not sure how to setup a backup here. Doing it with coolifies s3 backup with hetzner s3 storage, aws s3 or volumes.
Any recommendations here?
regards
The text was updated successfully, but these errors were encountered: