Building with grunt
agagancarczyk opened this issue · 19 comments
Hi Galvin,
After building the app with grunt, the blank server instance opens on localhost:9002 in my browser. Any idea on how to get it displaying the graph on localhost:9002. Many thanks
P.S. I'm new to Yeoman-Bower-Grunt but very enthusiastic about it and eager to learn with a bit of help. Any suggestions on a very good tutorial?
Hello @agagancarczyk,
Did you first run
npm install
bower install
and then
grunt serve
Afterwards grunt will open a new browser window to localhost:9002 which should display the exact same as you see here. If your issue persists can you open up your browsers console and report any errors you see here (or if you got any in your terminal from grunt)
Let us know how it goes!
Hi John,
Thanks for your quick reply. I followed all the instructions of running npm
install, bower install and grunt serve. Grunt opens a new browser window to
localhost:9002 but it's displaying blank/ white page.
I enclose the output from chrome's browser console. I'm getting no errors
in my terminal from grunt, screenshot attached.
Thanks.
Regards,
Agnieszka
On Thu, Jun 26, 2014 at 2:19 PM, Joel Kuntz notifications@github.com
wrote:
Hello @agagancarczyk https://github.com/agagancarczyk,
Did you first run
npm install
bower installand then
grunt serve
Afterwards grunt will open a new browser window to localhost:9002 which
should display the exact same as you see here
http://glavin001.github.io/ember-c3/dist/. If your issue persists can
you open up your browsers console and report any errors you see here (or if
you got any in your terminal from grunt)Let us know how it goes!
—
Reply to this email directly or view it on GitHub
#4 (comment).
I think you missed the screenshot / console log
Also can you see the graph here? Do you have any console errors there?
Hi Joel,
Screenshot attached (sorry I know it's very small) and yes I can see the
graph when I navigate to http://glavin001.github.io/ember-c3/dist/.
Thanks.
Kind Regards,
Agnieszka
On Thu, Jun 26, 2014 at 3:10 PM, Joel Kuntz notifications@github.com
wrote:
Also can you see the graph here
http://glavin001.github.io/ember-c3/dist/?—
Reply to this email directly or view it on GitHub
#4 (comment).
Hey Agnieszka
I think the problem is you are attempting to attach the screenshot via an email reply to this issue. Github apparently doesn't add the attachment into the issue comment. Could you please upload it via the Github web interface here
Thanks
Joel
Hi Joel,
Here you go.
Are you able to open them? If not I'll come up with something else. Thanks.
Kind Regards,
Agnieszka
Thats perfect Agnieszka, thank you.
It appears the server isn't recognizing/serving the dependencies properly. I'm not sure on an immediate fix and maybe @Glavin001 will know more.
Can you try the following and report back how it goes
-
Ensure grunt is installed globally
npm install -g grunt-cli -
Delete the directory you cloned this repository into and reclone it
git clone https://github.com/Glavin001/ember-c3.git -
Reinstall the dependencies and then try serving again
npm install
bower install
grunt serve
Hi Joel,
I followed all your instructions and all goes well except when running 'bower install'. Here is the error that I'm getting. Thanks
Alright, I've updated the dependencies so hopefully that does it for you.
-
update your repo
git pull origin master -
Reinstall dependencies and serve
npm install
bower install
grunt serve
It didn't help :(. Still the same problem with the bower. I even tried to remove the repo and clone it again and reinstall dependencies and serve.
Can you tell me what your version numbers are?
grunt -version
npm -version
bower -version
Sure,
grunt-cli v0.1.13
grunt v0.4.5
npm 1.4.9
bower 1.3.3
Can you try updating your npm and bower and then repeating the process before
npm update -g npm
npm update -g bower
Ok, still no joy. I updated npm and bower. Versions of both didn't change (npm 1.4.9 bower 1.3.3). I repeated the process of updating the repo, installing dependencies and serving and I noticed that running 'npm install' is producing this warning:
. Thanks
They should have updated npm to 1.4.16 and bower to 1.3.5 but I doubt that is what is causing the issue here.
I also get that warning but it doesn't seem to cause any issues. I'm sorry to say but I'm not sure what is causing the issue here. It will be best to wait for @Glavin001 as he will likely spot it instantly 😉
Thanks Joel. I'll wait for Glavin so :).
Probable Options
@agagancarczyk, here are your likely options:
- You are behind a firewall that is blocking github.com, which I believe is unlikely given you can login and use the github.com website and IP address. However, the firewall could be blocking more specifically the specific ports that are being used for cloning via
git://. In this case, SSH, so port 22.
or - You have not setup your SSH key with GitHub and so the SSH requests for cloning from GitHub are of course failing. I noticed that @Frozenfire92 suggested you clone with
git clone https://github.com/Glavin001/ember-c3.git. You should have been cloning withgit@github.com:Glavin001/ember-c3.gitthat uses SSH. If you have not setup your SSH key with Github, this would have failed, and then we would have known to get you setup with an SSH key 😉. Always use the SSH GitHub clone URL unless you absolutely cannot, such as option 1 where you are behind a firewall blocking port 22 for SSH.
Next Steps to Diagnose Your Case
Run the following in your Terminal:
ssh -Tv git@github.comWhat is the full response? Please copy and paste the text in reply here.
This will tell us if you have already successfully created your SSH key for GitHub.
If you have not already created your SSH key for GitHub please see https://help.github.com/articles/generating-ssh-keys
If you do not wish to setup a SSH key for GitHub and/or if you are in fact behind a firewall that is blocking SSH, please run the following:
git config --global url."https://".insteadOf git://Let me know how it goes.
@agagancarczyk let me know if this is still an issue and I can reopen this.