Closed begedin closed 9 years ago
There's a question of how to handle the following...
By default, ember new app-name
will create an app with ember-cli-content-security-policy
as a dependency. The default app settings will prevent the application from running due to several of the default content security policies. The following settings are required to be present in the app's configuration file into the exported ENV
object in order for the app to run without issues:
contentSecurityPolicyHeader: 'Content-Security-Policy',
contentSecurityPolicy: {
'default-src': "'self' accounts.google.com content.googleapis.com drive.google.com",
'script-src': "'self' 'unsafe-eval' 'unsafe-inline' apis.google.com drive.google.com",
'font-src': "'self'",
'connect-src': "'self' 'unsafe-eval' apis.google.com drive.google.com",
'img-src': "'self' data: ssl.gstatic.com csi.gstatic.com",
'style-src': "'self' 'unsafe-inline'",
'media-src': "'self'"
},
We have a couple of options, but I haven't explored them too deeply yet. I will create an issue for this so we can discuss it separately - #101
Errors thrown due to a missing configuration property should be as verbose as possible. in order to provide the user with enough information to get their app working with ember-gdrive.
As mentioned on slack, I'll be going through a fresh ember app and adding ember-gdrive to it.
During that process, I will try to run the app after each step, starting after
This should hopefully catch most of the errors.