{"action":"created","issue":{"url":"https://api.github.com/repos/dogestry/dogestry/issues/110","repository_url":"https://api.github.com/repos/dogestry/dogestry","labels_url":"https://api.github.com/repos/dogestry/dogestry/issues/110/labels{/name}","comments_url":"https://api.github.com/repos/dogestry/dogestry/issues/110/comments","events_url":"https://api.github.com/repos/dogestry/dogestry/issues/110/events","html_url":"https://github.com/dogestry/dogestry/issues/110","id":141967324,"number":110,"title":"Add ability to delete images","user":{"login":"dselans","id":1938759,"avatar_url":"https://avatars.githubusercontent.com/u/1938759?v=3","gravatar_id":"","url":"https://api.github.com/users/dselans","html_url":"https://github.com/dselans","followers_url":"https://api.github.com/users/dselans/followers","following_url":"https://api.github.com/users/dselans/following{/other_user}","gists_url":"https://api.github.com/users/dselans/gists{/gist_id}","starred_url":"https://api.github.com/users/dselans/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dselans/subscriptions","organizations_url":"https://api.github.com/users/dselans/orgs","repos_url":"https://api.github.com/users/dselans/repos","events_url":"https://api.github.com/users/dselans/events{/privacy}","received_events_url":"https://api.github.com/users/dselans/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/dogestry/dogestry/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-03-18T20:16:13Z","updated_at":"2016-05-16T09:56:29Z","closed_at":null,"body":"It would be nice to have some functionality in dogestry which allows one to delete images (and all associated, unused layers)."},"comment":{"url":"https://api.github.com/repos/dogestry/dogestry/issues/comments/219390093","html_url":"https://github.com/dogestry/dogestry/issues/110#issuecomment-219390093","issue_url":"https://api.github.com/repos/dogestry/dogestry/issues/110","id":219390093,"user":{"login":"relistan","id":267761,"avatar_url":"https://avatars.githubusercontent.com/u/267761?v=3","gravatar_id":"","url":"https://api.github.com/users/relistan","html_url":"https://github.com/relistan","followers_url":"https://api.github.com/users/relistan/followers","following_url":"https://api.github.com/users/relistan/following{/other_user}","gists_url":"https://api.github.com/users/relistan/gists{/gist_id}","starred_url":"https://api.github.com/users/relistan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/relistan/subscriptions","organizations_url":"https://api.github.com/users/relistan/orgs","repos_url":"https://api.github.com/users/relistan/repos","events_url":"https://api.github.com/users/relistan/events{/privacy}","received_events_url":"https://api.github.com/users/relistan/received_events","type":"User","site_admin":false},"created_at":"2016-05-16T09:56:29Z","updated_at":"2016-05-16T09:56:29Z","body":"Totally. \r\n\r\nBut, this requires a level of accounting which Dogestry does not currently implement. To implement this currently, you'd have to crawl all the images and account for the layers, while assuming that no other clients are making changes while you do it. \r\n\r\nKeeping this state with a distributed client might be interesting given the number of race conditions that are possible. S3 doesn't implement atomic operations so locking would need to be accomplished in another system. \r\n\r\nFinally, keeping state would be much more easily accomplished by adding a dependency on Dynamo or at least SimpleDB. Are people up for that?"}}