{"action":"opened","issue":{"url":"https://api.github.com/repos/superacidjax/ember-cli-deploy-fastly/issues/1","repository_url":"https://api.github.com/repos/superacidjax/ember-cli-deploy-fastly","labels_url":"https://api.github.com/repos/superacidjax/ember-cli-deploy-fastly/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/superacidjax/ember-cli-deploy-fastly/issues/1/comments","events_url":"https://api.github.com/repos/superacidjax/ember-cli-deploy-fastly/issues/1/events","html_url":"https://github.com/superacidjax/ember-cli-deploy-fastly/issues/1","id":180698899,"number":1,"title":"Open Discussion: Architecture","user":{"login":"jamesarosen","id":2406,"avatar_url":"https://avatars.githubusercontent.com/u/2406?v=3","gravatar_id":"","url":"https://api.github.com/users/jamesarosen","html_url":"https://github.com/jamesarosen","followers_url":"https://api.github.com/users/jamesarosen/followers","following_url":"https://api.github.com/users/jamesarosen/following{/other_user}","gists_url":"https://api.github.com/users/jamesarosen/gists{/gist_id}","starred_url":"https://api.github.com/users/jamesarosen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jamesarosen/subscriptions","organizations_url":"https://api.github.com/users/jamesarosen/orgs","repos_url":"https://api.github.com/users/jamesarosen/repos","events_url":"https://api.github.com/users/jamesarosen/events{/privacy}","received_events_url":"https://api.github.com/users/jamesarosen/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-10-03T17:32:01Z","updated_at":"2016-10-03T17:32:01Z","closed_at":null,"body":"I haven't dug into ember-cli-deploy for about a year -- since when the v0.5.0 rewrite was in-progress -- so please forgive me if I'm off-track here. I want to help, but I'm not an expert on ember-cli-deploy.\r\n\r\nFastly Edge Dictionaries can't take a huge amount of data. Each item value can only be up to 8000 characters.\r\n\r\nSo we have two options for a Fastly index plugin:\r\n\r\n 1. Put whole files in the dictionary\r\n   * on build, if `index.html` is > 8000 characters, throw an error and stop the build\r\n   * on build, if `index.html` is > 6000 characters (customizable?), print a warning\r\n   * on build, write commit `abcdef`'s `index.html` with `PUT /service/service_id/dictionary/index-html/item/abcdef`\r\n   * to activate `abcdef`, write the current pointer with `PUT /service/service_id/dictionary/index-html/item/current` with `abcdef`\r\n 1. Put whole files somewhere else\r\n   * on build, rename `index.html` to `index-abcdef.html`\r\n   * let the _asset_ plugin upload `index-abcdef.html` to S3 or whatever persistent store you're using\r\n   * to activate `abcdef`, write the current pointer with `PUT /service/service_id/dictionary/index-html/item/current` with `abcdef`\r\n\r\nIn the first case, it will also be important to _prune_ the `/service/service_id/dictionary/index-html/item/*` entries regularly. If that dictionary gets large (MB), it could degrade the quality of service."}}
{"actor":{"display_login":"jamesarosen"}}