ga-wdi-boston / capstone-project

Other
3 stars 28 forks source link

Deployment issue: sign up/ in and everything else not working. #436

Closed ielole closed 7 years ago

ielole commented 7 years ago

I'm getting this error when I try to sign up on my deployed app.

Uncaught Error: Could not find module `https://warm-refuge-42424.herokuapp.com/config/environment` imported from `learn-to-app/ajax/service`
raq929 commented 7 years ago

It's not finding the environment file. Make sure that it's there on gh-pages on github?

raq929 commented 7 years ago

I think you might have missed a step in deployment.

ielole commented 7 years ago

I looked over the steps and I know that I did each step

payne-chris-r commented 7 years ago

Did I share this with the class? #330 Please review it.

ielole commented 7 years ago

I've looked at the issue referred to above and the only thing that I didn't do was comment out /dist in ~/.gitignore, which I'm not sure how to locate. I've done everything else.

ielole commented 7 years ago

I've gone through trying to deploy again and have gotten the same result. Could someone go through the process with me to point out what I'm missing?

raq929 commented 7 years ago

We can come by in a bit. If you don't have a dist/ folder on gh-pages, that's definitely the problem. Can you post your .gitignore?

ielole commented 7 years ago

The gh-pages version is below:


# Created by https://www.gitignore.io/api/node,osx,linux,windows,ruby,node,rails,express,ember

### Node ###
# Logs
logs
*.log
npm-debug.log*

# Runtime data
pids
*.pid
*.seed
*.pid.lock

# Directory for instrumented libs generated by jscoverage/JSCover
lib-cov

# Coverage directory used by tools like istanbul
coverage

# nyc test coverage
.nyc_output

# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
.grunt

# node-waf configuration
.lock-wscript

# Compiled binary addons (http://nodejs.org/api/addons.html)
build/Release

# Dependency directories
node_modules
jspm_packages

# Optional npm cache directory
.npm

# Optional eslint cache
.eslintcache

# Optional REPL history
.node_repl_history

### OSX ###
*.DS_Store
.AppleDouble
.LSOverride

# Icon must end with two \r
Icon

# Thumbnails
._*

# Files that might appear in the root of a volume
.DocumentRevisions-V100
.fseventsd
.Spotlight-V100
.TemporaryItems
.Trashes
.VolumeIcon.icns
.com.apple.timemachine.donotpresent

# Directories potentially created on remote AFP share
.AppleDB
.AppleDesktop
Network Trash Folder
Temporary Items
.apdisk

### Linux ###
*~

# temporary files which can be created if a process still has a handle open of a deleted file
.fuse_hidden*

# KDE directory preferences
.directory

# Linux trash folder which might appear on any partition or disk
.Trash-*

### Windows ###
# Windows image file caches
Thumbs.db
ehthumbs.db

# Folder config file
Desktop.ini

# Recycle Bin used on file shares
$RECYCLE.BIN/

# Windows Installer files
*.cab
*.msi
*.msm
*.msp

# Windows shortcuts
*.lnk

### Ruby ###
*.gem
*.rbc
/.config
/coverage/
/InstalledFiles
/pkg/
/spec/reports/
/spec/examples.txt
/test/tmp/
/test/version_tmp/
/tmp/

# Used by dotenv library to load environment variables.
# .env

## Specific to RubyMotion:
.dat*
.repl_history
build/
*.bridgesupport
build-iPhoneOS/
build-iPhoneSimulator/

## Specific to RubyMotion (use of CocoaPods):
#
# We recommend against adding the Pods directory to your .gitignore. However
# you should judge for yourself, the pros and cons are mentioned at:
# https://guides.cocoapods.org/using/using-cocoapods.html#should-i-check-the-pods-directory-into-source-control
#
# vendor/Pods/

## Documentation cache and generated files:
/.yardoc/
/_yardoc/
/doc/
/rdoc/

## Environment normalization:
/.bundle/
/vendor/bundle
/lib/bundler/man/

# for a library or gem, you might want to ignore these files since the code is
# intended to run in multiple environments; otherwise, check them in:
# Gemfile.lock
# .ruby-version
# .ruby-gemset

# unless supporting rvm < 1.11.0 or doing something fancy, ignore this:
.rvmrc

### Node ###
# Logs
logs
*.log
npm-debug.log*

# Runtime data
pids
*.pid
*.seed
*.pid.lock

# Directory for instrumented libs generated by jscoverage/JSCover
lib-cov

# Coverage directory used by tools like istanbul
coverage

# nyc test coverage
.nyc_output

# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
.grunt

# node-waf configuration
.lock-wscript

# Compiled binary addons (http://nodejs.org/api/addons.html)
build/Release

# Dependency directories
node_modules
jspm_packages

# Optional npm cache directory
.npm

# Optional eslint cache
.eslintcache

# Optional REPL history
.node_repl_history

### Rails ###
*.rbc
capybara-*.html
# .rspec - we want developers to have this file available
/log
/tmp
/db/*.sqlite3
/db/*.sqlite3-journal
/public/system
/coverage/
/spec/tmp
**.orig
rerun.txt
pickle-email-*.html

# TODO Comment out this rule if you are OK with secrets being uploaded to the repo
config/initializers/secret_token.rb

# Only include if you have production secrets in this file, which is no longer a Rails default
# config/secrets.yml

# dotenv
# TODO Comment out this rule if environment variables can be committed
.env

## Environment normalization:
/.bundle
/vendor/bundle

# these should all be checked in to normalize the environment:
# Gemfile.lock, .ruby-version, .ruby-gemset

# unless supporting rvm < 1.11.0 or doing something fancy, ignore this:
.rvmrc

# if using bower-rails ignore default bower_components path bower.json files
/vendor/assets/bower_components
# *.bowerrc - needed in ember-template, etc.
# bower.json - ditto

# Ignore pow environment settings
.powenv

# Ignore Byebug command history file.
.byebug_history

#!! ERROR: express is undefined. Use list command to see defined gitignore types !!#

### Ember ###
# see https://github.com/ember-cli/ember-cli/blob/master/blueprints/app/files/gitignore
# compiled output
#/dist
/tmp

# dependencies
/node_modules
/bower_components

# misc
/.sass-cache
/connect.lock
/coverage/*
/libpeerconnection.log
npm-debug.log
testem.log
raq929 commented 7 years ago

Yeah, you need to uncomment dist.

it's here:

### Ember ###
# see https://github.com/ember-cli/ember-cli/blob/master/blueprints/app/files/gitignore
# compiled output
#/dist
/tmp
raq929 commented 7 years ago

Then build again.

raq929 commented 7 years ago

What's your status?

ielole commented 7 years ago

...being referred to Antony

raq929 commented 7 years ago

Is this resolved? Please close if it is.

ielole commented 7 years ago

So, when using the ember deployment guide: https://github.com/ga-wdi-boston/ember-deployment-guide, I got confused when I reached this part of the guide -->

  1. Now you have to ensure you have your application/adapter and ajax files import the apiHost link. In application/adapter file:
    
    import ActiveModelAdapter from 'active-model-adapter';
    import ENV from '<% ember-deployment-example name %>/config/environment';

export default ActiveModelAdapter.extend({ host: ENV.apiHost, ... ... ... });

IF/WHEN you have a ajax/service file:
```js
import AjaxService from 'ember-ajax/services/ajax';
import ENV from '<% ember-deployment-example name %>/config/environment';

export default AjaxService.extend({
  host: ENV.apiHost,
  ...
  ...
  ...
});

I thought that '<% ember-deployment-example name %>' was different than '<% NAME OF YOUR CLIENT will be here %>', BUT they are the same thing! And if you did the 'Find in Project' and found 11 instances of your 'app name' in 9 files, then these 2 files will already have the your app name before the first '/', and they won't need to be edited.

After changing the beginning parts of the file paths above, disregarding

var ENV = {

and INSTEAD keeping

'use strict';
  const ENV = {

and DELETING the remote branch of gh-pages, after getting this error:

 ! [rejected]        5897a7a041fb9ae94027b147473735bb63f4aee9 -> gh-pages (non-fast-forward)
error: failed to push some refs to 'git@github.com:ielole/learn-to-front-end.git'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

by typing (git push origin :gh-pages) in the terminal and running

git subtree push --prefix dist origin gh-pages

... my front was successfully deployed.