Move URL used for fetching into fetcher.js directly to avoid config/environment bug

config/environment.js could be used for building (via meta tag) but not for tests.
See: glimmerjs/glimmer-application-pipeline#89
Once this is fixed application environment configuration can be consolidated in one spot.

Author: chadian

Diff for: config/environment.js

@@ -3,7 +3,6 @@
 module.exports = function(environment) {
   let ENV = {
     modulePrefix: 'vorfreude',
-    IMAGE_ENDPOINT_URL: 'https://vorfreude.now.sh/',
     environment
   };
 

Diff for: ember-cli-build.js

@@ -7,7 +7,7 @@ const json = require("rollup-plugin-json");
 
 module.exports = function(defaults) {
   let app = new GlimmerApp(defaults, {
-    storeConfigInMeta: true,
+    storeConfigInMeta: false,
     rollup: {
       plugins: [
         resolve({ jsnext: true, module: true, main: true }),

Diff for: package.json

@@ -1,5 +1,5 @@
 {
-  "name": "Vorfreude",
+  "name": "vorfreude",
   "version": "0.1.0",
   "description": "A countdown with a fresh wallpapered tab on every new tab",
   "directories": {

Diff for: src/utils/lib/fetcher.js

@@ -1,19 +1,8 @@
-import env from "../../../config/environment";
 import { take, clone } from "ramda";
 import shuffle from './shuffle';
 import { SimpleIndexedDbAdapter } from "./storage";
 
-// `typeof env === 'function'`
-// this is an unfortunate hack of this file being used for two builds:
-//
-// 1. Glimmer App - it resolves the env for correct ember build environment
-//
-// 2. /chrome build via rollup - the build of background.js via roll up includes
-// this file for background fetching. The import of 'env' is then unresolved and
-// still a function that requires a string of the environment to retrieve the
-// configuration. In this type of build the environment should be assumed to be
-// production.
-const { IMAGE_ENDPOINT_URL } = typeof env === 'function' ?  env('production') : env;
+const IMAGE_ENDPOINT_URL = 'https://vorfreude.now.sh/';
 
 const highQualityImageUrlForPhoto = photo => photo.url_o;