Since there is not yet any automated backup solution within Aegir, apart from cron scripts putting backups in the backups directory regularly, when using the frontend to backup, it would be useful to qualify the backup with a name to allow better recognition of what led to the (always through the frontend) user triggered backup.

Jun.

Comments

adrian’s picture

adrian CreditAttribution: adrian commented

there's already a field for it in the db, we just generate the text in the api.

so this could be a 2 line fix.

also. automated backups is coming soon.

adrian’s picture

adrian CreditAttribution: adrian commented
Status: Active » Fixed

added in HEAD

http://img.skitch.com/20100628-k2bb573amuneek87uufpaas7uu.jpg

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

jun’s picture

jun CreditAttribution: jun commented

Neat!

  • Commit e8bbbe5 on dev-dns, dev-features, dev-log_directory, dev-migrate_aliases, dev-multiserver-install, dev-newsiteform, dev-nginx, dev-ssl, prod-koumbit, dev-ssl-ip-allocation-refactor, dev-1205458-move_sites_out_of_platforms, 7.x-3.x, dev-588728-views-integration, dev-1403208-new_roles, dev-helmo-3.x by adrian: 
    allow naming of backups - #838044

  • Commit e8bbbe5 on dev-dns, dev-features, dev-log_directory, dev-migrate_aliases, dev-multiserver-install, dev-newsiteform, dev-nginx, dev-ssl, prod-koumbit, dev-ssl-ip-allocation-refactor, dev-1205458-move_sites_out_of_platforms, 7.x-3.x, dev-588728-views-integration, dev-1403208-new_roles, dev-helmo-3.x by adrian: 
    allow naming of backups - #838044