Closed germonprez closed 7 years ago
None of those are errors that will cause the install to be unsuccessful. How long are you waiting for the database to connect on the last screenshot?
10 minutes then I kill things.
On Mon, Apr 3, 2017 at 5:47 AM, Jake Harding notifications@github.com wrote:
None of those are errors that will cause the install to be unsuccessful. How long are you waiting for the database to connect on the last screenshot?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jakeharding/repo-health/issues/46#issuecomment-291109160, or mute the thread https://github.com/notifications/unsubscribe-auth/AAoDUOxQXflEf6ajmo2PzuI1NFaQ9YjBks5rsM5QgaJpZM4MxXWM .
-- Mutual of Omaha Associate Professor Information Systems College of Information Science & Technology University of Nebraska Omaha http://faculty.ist.unomaha.edu/mgermonprez/cv.txt
None of those warnings should be preventing you from running it. What happens if you run mysql -h 127.0.0.1 -P 3306 -umsr14 -pmsr14
in a different terminal while this is running? Does it connect?The reason the last part waits, is because it is running the msr14 mysql against the database before starting the mysql service. Normally it takes a few minutes (like 3-4).
Things are moving forward (admittedly I'm sort of taking a shotgun approach as I get ready for another class).
1) Mac --> Looks like just an Allowed Host issue.
2) Ubuntu --> Connection is hanging
3) Codefresh won't do it
Hmm , I don't know why on Mac it would say host not allowed. I haven't ran into that issue. With regards to Ubuntu, it looks like it is working based on the screenshot. Does it not show up at localhost:8000?
Ahhh!! So close. Both Ubuntu and Mac are giving the same
Nothing in the browser though
Log from Ubuntu
It looks like the ui didn't build. Can you try to run docker exec <web container> /bin/bash -c 'cd /www/repo-health/index/static && npm run dist'
again?
If this doesn't work, you will have to run the npm install && npm dist
locally in the repo-health/index/static
folder then run ./docker/clean.sh
and then build the docker container again with docker-compose
. Then it will pick up the local dist.
I don't know why it wouldn't have created the ui in the docker container, but I can take a look at that.
Sure, I'll give it a go after class.
On Mon, Apr 3, 2017 at 10:15 AM, Benjamin Parish notifications@github.com wrote:
It looks like the ui didn't build. Can you try to run docker exec <web container> /bin/bash -c 'cd /www/repo-health/index/static && npm run dist' again? If this doesn't work, you will have to run the npm install && npm dist locally in the repo-health/index/static folder then run ./docker/clean.sh and then build the docker container again with docker-compose. Then it will pick up the local dist. I don't know why it wouldn't have created the ui in the docker container, but I can take a look at that.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jakeharding/repo-health/issues/46#issuecomment-291174477, or mute the thread https://github.com/notifications/unsubscribe-auth/AAoDUDRFUmlMHX12elrsbBhb68lnWC88ks5rsQ0ogaJpZM4MxXWM .
-- Mutual of Omaha Associate Professor Information Systems College of Information Science & Technology University of Nebraska Omaha http://faculty.ist.unomaha.edu/mgermonprez/cv.txt
Or to make it easy you can just do a npm start
in the local repo-health/index/static
. Then head to localhost:3000
and it should work. That way you don't have to wait for it to build again.
Am I going to need nodeJS installed (needed for npm)?
On Mon, Apr 3, 2017 at 10:35 AM, Benjamin Parish notifications@github.com wrote:
Or to make it easy you can just do a npm start in the local repo-health/index/static. Then head to localhost:3000 and it should work. That way you don't have to wait for it to build again.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jakeharding/repo-health/issues/46#issuecomment-291180733, or mute the thread https://github.com/notifications/unsubscribe-auth/AAoDUK_uQ8V097mYEUjmMhzLzp2Pow6jks5rsRHCgaJpZM4MxXWM .
-- Mutual of Omaha Associate Professor Information Systems College of Information Science & Technology University of Nebraska Omaha http://faculty.ist.unomaha.edu/mgermonprez/cv.txt
If you are doing it on your local machine, yes. You should use the 7.x node version.
No go on either Mac or Ubuntu. Same errors on npm start.
That shouldn't matter because npm start
creates a proxy so, it should be tapping into only the server code and the ui would be brought up locally. localhost:3000
really doesn't work?
I'll try again. Order matter?
docker-compose up then npm start?
On Mon, Apr 3, 2017 at 11:59 AM, Benjamin Parish notifications@github.com wrote:
That shouldn't matter because npm start creates a proxy so, it should be tapping into the only the server code and the ui would be brought up locally. localhost:3000 really doesn't work?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jakeharding/repo-health/issues/46#issuecomment-291205326, or mute the thread https://github.com/notifications/unsubscribe-auth/AAoDUEP3X8O2j8QCQr7D6WYxrT8Cy5akks5rsSVXgaJpZM4MxXWM .
-- Mutual of Omaha Associate Professor Information Systems College of Information Science & Technology University of Nebraska Omaha http://faculty.ist.unomaha.edu/mgermonprez/cv.txt
Yeah and then go to localhost:3000
.
If that doesn't work, then I would honestly just do npm run dist
from /repo-health/index/static
folder and then run ./docker/clean.sh
from the root folder and then do a docker-compose up
.
Order really shouldn't matter though since webpack will try to connect each time the page is loaded.
Nice!
How long does the generation take?
On my local machine, it takes roughly 3-5 seconds :cry:. Is it even showing up for you?
What I posted is what I see. This for two different repos. I could try on my Mac.
On Mon, Apr 3, 2017 at 12:33 PM, Benjamin Parish notifications@github.com wrote:
On my local machine, it takes roughly 3-5 seconds 😢. Is it even showing up for you?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jakeharding/repo-health/issues/46#issuecomment-291215330, or mute the thread https://github.com/notifications/unsubscribe-auth/AAoDUGFYCneiMCHh7ObdQB-0izuobhjrks5rsS1ggaJpZM4MxXWM .
-- Mutual of Omaha Associate Professor Information Systems College of Information Science & Technology University of Nebraska Omaha http://faculty.ist.unomaha.edu/mgermonprez/cv.txt
If you open up the console, what do you see in the network tab?
More detail please.
On Mon, Apr 3, 2017 at 12:35 PM, Benjamin Parish notifications@github.com wrote:
If you open up the console, what do you see in the network tab?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jakeharding/repo-health/issues/46#issuecomment-291215893, or mute the thread https://github.com/notifications/unsubscribe-auth/AAoDUEvlwpegF0yYn0KWScyC5adNkjZ0ks5rsS3XgaJpZM4MxXWM .
-- Mutual of Omaha Associate Professor Information Systems College of Information Science & Technology University of Nebraska Omaha http://faculty.ist.unomaha.edu/mgermonprez/cv.txt
On mac CMD + Option + i
to open the devtools. Then click on the network tab and then reload the page.
@germonprez Go ahead and give it a shot again. Pull down the latest code on your local machine and do a ./docker/clean.sh
and then do a docker-compose up
. It should work now! :)
Not going to like this.
Same on Ubuntu and Mac:
1) Clone 2) Clean 3) Docker-compose up 4) Just the app page 5) Tried npm run dist --> Generated those errors on the right.
Hmm, I was getting exactly what you were getting before then blew everything out and restarted and it works from beginning to end. The only thing I can really say is to again blow everything out. Do a rm -r /repo_health/index/static/dist
and then do the clean/sh
script again. You shouldn't need to do anything locally anymore. But if you wanted to be for sure, you would have to run npm install && npm run dist
before the docker-compose up
.
OR you can do the local web ui. So just do a npm start
in the /repo_health/index/static
folder and it should again proxy into the docker instance. localhost:3000 will be the url
@germonprez I am on campus and can swing by to help if you want. It is hard to see what is going on from the screenshots.
Give me a second. I haven't had much time for this today.
On Tue, Apr 4, 2017 at 2:33 PM, Jake Harding notifications@github.com wrote:
@germonprez https://github.com/germonprez I am on campus and can swing by to help if you want. It is hard to see what is going on from the screenshots.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jakeharding/repo-health/issues/46#issuecomment-291608041, or mute the thread https://github.com/notifications/unsubscribe-auth/AAoDUJowflYL13nXzEORwRnO8195-sUDks5rspsVgaJpZM4MxXWM .
-- Mutual of Omaha Associate Professor Information Systems College of Information Science & Technology University of Nebraska Omaha http://faculty.ist.unomaha.edu/mgermonprez/cv.txt
Sure thing. Let me know when.
I'm available if you have time between now and 3:30
On Tue, Apr 4, 2017 at 2:40 PM, Jake Harding notifications@github.com wrote:
Sure thing. Let me know when.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jakeharding/repo-health/issues/46#issuecomment-291609784, or mute the thread https://github.com/notifications/unsubscribe-auth/AAoDUJsOIMFDgG-1Ni6t1Fc8YAKiLkNsks5rspymgaJpZM4MxXWM .
-- Mutual of Omaha Associate Professor Information Systems College of Information Science & Technology University of Nebraska Omaha http://faculty.ist.unomaha.edu/mgermonprez/cv.txt
This issue appears to be because the volume that is mounted in to the container is masking the dist folder created when building the Docker image. It is explained well here and normal behavior but there must be some work around. @bparish628 Any ideas?
@jakeharding
One of the comments says:
If you use an Entrypoint script it will run at container startup after the volumes have been mounted.
We should maybe add the npm run dist/ npm install
to it probably.
Ready for another install on my end from newest repo?
On Wed, Apr 5, 2017 at 8:48 AM, Benjamin Parish notifications@github.com wrote:
@jakeharding https://github.com/jakeharding One of the comments says: If you use an Entrypoint script it will run at container startup after the volumes have been mounted.
We should maybe add the npm run dist/ npm install to it probably.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jakeharding/repo-health/issues/46#issuecomment-291866781, or mute the thread https://github.com/notifications/unsubscribe-auth/AAoDUP9EskRg00uJJu5WZGOiyUPcMuHkks5rs5urgaJpZM4MxXWM .
-- Mutual of Omaha Associate Professor Information Systems College of Information Science & Technology University of Nebraska Omaha http://faculty.ist.unomaha.edu/mgermonprez/cv.txt
@bparish628 I did try that but that isn't saying I did it correctly.
@germonprez Master has been updated so you can pull in the changes to your local. I would suggest running the clean script then run docker-compose up
.
Will do
On Wed, Apr 5, 2017 at 10:05 AM, Jake Harding notifications@github.com wrote:
@germonprez https://github.com/germonprez Master has been updated so you can pull in the changes to your local. I would suggest running the clean script then run docker-compose up.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jakeharding/repo-health/issues/46#issuecomment-291891172, or mute the thread https://github.com/notifications/unsubscribe-auth/AAoDUJ6CkIh1YUQZ5tF7pSA2NBfkG-1Eks5rs63IgaJpZM4MxXWM .
-- Mutual of Omaha Associate Professor Information Systems College of Information Science & Technology University of Nebraska Omaha http://faculty.ist.unomaha.edu/mgermonprez/cv.txt
I would also like to remind you the dataset we are using is old and some current repos are not in present, like the BusyBox repo in the previous screenshot.
Could you give me one or two URLs you have tested on?
On Wed, Apr 5, 2017 at 10:10 AM, Jake Harding notifications@github.com wrote:
I would also like to remind you the dataset we are using is old and some current repos are not in present, like the BusyBox repo in the previous screenshot.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jakeharding/repo-health/issues/46#issuecomment-291892891, or mute the thread https://github.com/notifications/unsubscribe-auth/AAoDUJ03lEKvPGqDrIvQYKHIeaRzCq-2ks5rs67_gaJpZM4MxXWM .
-- Mutual of Omaha Associate Professor Information Systems College of Information Science & Technology University of Nebraska Omaha http://faculty.ist.unomaha.edu/mgermonprez/cv.txt
These two work: cakephp/cakephp django/django
Right on!
I simply can't get the Docker way of things rolling. I've tried many different ways at this:
1) Ubuntu 14+, 16+, Amazon Linux, Mac OSX, 2) Running Parallels, Local, AWS, Codefresh.io 3) Running different variants of sudo and su 4) Ultimately, the process completes 85% of the way but a few Warnings and Connection problems (Codefresh builds but doesn't launch). These are a few of the shots I took from my last attempt (same errors across all).