host front end on the actual domain

EricLScace commented 6 years ago

First task is to get grunt to deploy on GitHub. Right now:

GitHub deploys Master branch as a blank page.

Grunt deploy generates this warning and aborts:


Running "webpack:build" (webpack) task
Warning: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
- configuration.module.loaders[2] has an unknown property 'includePaths'. These properties are valid:
object { enforce?, exclude?, include?, issuer?, loader?, loaders?, oneOf?, options?, parser?, query?, resource?, resourceQuery?, compiler?, rules?, test?, use? }
-> A rule Use --force to continue.

Aborted due to warnings.



Changing `includePaths` to `include` appears to fix this.

EricLScace commented 6 years ago

Running grunt serve locally generates error

grunt serve
Running "webpack-dev-server:start" (webpack-dev-server) task
Warning: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
 - configuration has an unknown property 'debug'. These properties are valid:
   object { amd?, bail?, cache?, context?, dependencies?, devServer?, devtool?, entry, externals?, loader?, module?, name?, node?, output?, parallelism?, performance?, plugins?, profile?, recordsInputPath?, recordsOutputPath?, recordsPath?, resolve?, resolveLoader?, stats?, target?, watch?, watchOptions? }
   The 'debug' property was removed in webpack 2.
   Loaders should be updated to allow passing this option via loader options in module.rules.
   Until loaders are updated one can use the LoaderOptionsPlugin to switch loaders into debug mode:
   plugins: [
     new webpack.LoaderOptionsPlugin({
       debug: true
     })
   ] Use --force to continue.

Temporarily commented out both debug: true and keepAlive: true in webpack-dev-server.js to expose other errors. Ref #56 and commit https://github.com/EricLScace/All-the-Matrices-front-end/commit/c2b2dec49b01c19b7fdbb8f1ad2cf00f3c40bca6

EricLScace commented 6 years ago

Running grunt deploy on master resulted in:

Running "webpack:build" (webpack) task
Hash: bd6204cdee2103ff6754                                                         
Version: webpack 3.10.0
Time: 583ms
    Asset    Size  Chunks                    Chunk Names
vendor.js  341 kB       0  [emitted]  [big]  vendor
   [0] ./node_modules/jquery/dist/jquery.js 268 kB {0} [built]
       single entry jquery [1] multi jquery bootstrap-sass vendor:100000
       cjs require jQuery [2] ./node_modules/bootstrap-sass/assets/javascripts/bootstrap.js 1:0-17
   [1] multi jquery bootstrap-sass 40 bytes {0} [built]
   [2] ./node_modules/bootstrap-sass/assets/javascripts/bootstrap.js 69.7 kB {0} [built]
       single entry bootstrap-sass [1] multi jquery bootstrap-sass vendor:100001

ERROR in Entry module not found: Error: Can't resolve 'babel' in '/Users/EricScace/wdi/projects/All-the-Matrices-front'
BREAKING CHANGE: It's no longer allowed to omit the '-loader' suffix when using loaders.
                 You need to specify 'babel-loader' instead of 'babel',
                 see https://webpack.js.org/guides/migrating/#automatic-loader-module-name-extension-removed

ERROR in Entry module not found: Error: Can't resolve 'babel' in '/Users/EricScace/wdi/projects/All-the-Matrices-front'
BREAKING CHANGE: It's no longer allowed to omit the '-loader' suffix when using loaders.
                 You need to specify 'babel-loader' instead of 'babel',
                 see https://webpack.js.org/guides/migrating/#automatic-loader-module-name-extension-removed
Warning:  Use --force to continue.

EricLScace commented 6 years ago

Error: Can't resolve 'expose' in '/Users/EricScace/wdi/projects/All-the-Matrices-front'
BREAKING CHANGE: It's no longer allowed to omit the '-loader' suffix when using loaders.
                 You need to specify 'expose-loader' instead of 'expose',
                 see https://webpack.js.org/guides/migrating/#automatic-loader-module-name-extension-removed
@ ./assets/scripts/authn-api.js 1:0-17
 @ ./assets/scripts/authn-login-ui.js
 @ ./assets/scripts/authn-dispatch-ui.js
 @ ./assets/scripts/index.js
 @ ./index.js
 @ multi (webpack)-dev-server/client?http://localhost:7165 ./index.js

Addressed in commit 19a641c

EricLScace commented 6 years ago

ERROR in ./sass/index.scss
Module parse failed: Unexpected token (1:15)
You may need an appropriate loader to handle this file type.
| $icon-font-path: '~bootstrap-sass/assets/fonts/bootstrap/';
| @import '~bootstrap-sass/assets/stylesheets/bootstrap';
| @import './colors';
 @ ./index.js 12:0-28
 @ multi (webpack)-dev-server/client?http://localhost:7165 ./index.js

Fixed in commit https://github.com/EricLScace/All-the-Matrices-front-end/commit/9e5612080a6f2c7df11db0728ed48488542e10ed

EricLScace commented 6 years ago

AWS Code Deploy — Cloud Academy tutorial AWS' tutorial using CodeDeploy to deploy an app from GitHub

Notes: • CodeDeploy is one of 3 AWS tools: CodeDeploy, CodeCommit and CodePipeline.

Code to be deployed is stored in Amazon S3 as a Application Revision. .git is not included in the Application Revision.
Instructions for how to deploy (a component of CodeDeploy) is specified in the AppSpec file, saved as <application-root>/appspec.yml.

EricLScace commented 6 years ago

This tutorial may be helpful. Note that part 2 covers infrastructure maintenance & devops.

EricLScace / All-the-Matrices-front-end

host front end on the actual domain #45