Is the site down?

Question

Is the site down?

tiagojdf opened this issue 9 years ago · comments

Tiago Ferreira commented 9 years ago

It seems your website is down.

Kristoffer Brabrand · Answer 1 · Mon Sep 28 2015 23:37:51 GMT+0800 (China Standard Time)

Up again now. Wish we had a good explanation other than too little time. Sorry.

Tiago Ferreira · Answer 2 · Tue Sep 29 2015 02:50:02 GMT+0800 (China Standard Time)

I am trying to run your project locally so I can contribute, but I don't seem to understand how the whole installation and deployment of the project works. I have done an npm install and I have tried running the webpack-dev-server, but it seems I am missing some compilation step that would allow me to turn the jsx into html. What is the current workflow regarding both serving the front and back end ?

Kristoffer Brabrand · Answer 3 · Tue Sep 29 2015 03:10:20 GMT+0800 (China Standard Time)

I checked just now, and to get it up and running locally this should be it:

Install redis
Clone repo
npm install

Now the app should be ready to be run. While developing gulp watch is probably what you want. With regards to how to run in in production we haven't had/taken the time to set it up properly. Right now we're just doing forever node index.js.

Sorry that this is not documentet somewhere.. But hope that this helps a bit 😄

Tiago Ferreira · Answer 4 · Fri Oct 02 2015 05:45:47 GMT+0800 (China Standard Time)

I am getting

Segmentation fault 11

It seems it could be due to hiredis. I have tried reinstalling it, but I am getting an error (I think it is due to my version of node). What version of node are you using ?

Now I am getting an error during npm install. I will try again tomorrow and let you know once I have more details on the actual problem.

Tiago Ferreira · Answer 5 · Sat Oct 03 2015 21:33:02 GMT+0800 (China Standard Time)

It seems my problem was a conflict with my xcode and the fact that I was using gcc from macports.In the end I fixed it and am now able to install the project, using node (v0.12.7).

However, when I run gulp watch I get the following:

[15:08:52] Using gulpfile ~/Documents/projects/react-components/gulpfile.js
[15:08:52] Starting 'serve'...
[15:08:53] Finished 'serve' after 659 ms
[15:08:53] Starting 'webpack:build-dev'...
Server running at: http://Tiago-MacBook-Pro.local:3000
error: Failed to fetch modules from DB: No modules returned

Any ideia what might be the problem ?

Kristoffer Brabrand · Answer 6 · Mon Oct 05 2015 02:56:23 GMT+0800 (China Standard Time)

That is probably because you don't have any modules in you DB. Running the module import script will probably fix it. Pointers @rexxars?

Tiago Ferreira · Answer 7 · Mon Oct 05 2015 14:22:31 GMT+0800 (China Standard Time)

And what script would that be?

Espen Hovlandsdal · Answer 8 · Mon Oct 05 2015 15:44:51 GMT+0800 (China Standard Time)

node cron/fetch-components.js. I'll try to make a setup guide in the README today or tomorrow.

Espen Hovlandsdal · Answer 9 · Mon Oct 05 2015 15:45:44 GMT+0800 (China Standard Time)

I know that a lot of the dependencies we are using are pretty old. Might cause some problems on Node 4 etc. I'll look into that aswell.

Tiago Ferreira · Answer 10 · Tue Oct 06 2015 01:12:22 GMT+0800 (China Standard Time)

@rexxars I have been documenting what I have done so far, so I can do that as my first contribution to the project if you want me to. I have been using nvm with node v0.12.7 (npm v2.11.3) for the time being