Closed mikeumus closed 8 years ago
If that hangs at the point you show in the picture, that's where Meteor is building the app. That unfortunately always takes a long time on first run. You have 2.5gb of RAM (which should be enough), but what do you have for CPU? That initial startup takes a long time on my MacBook Pro (which surely has more CPU power than the virtual machine they give you), so I suspect it's just taking longer than you expected it would. Then when you stopped it and restarted with Meteor, it had already been partially built and went faster that time. Not sure what else it could be. reaction-cli
is literally just running that same command under the hood.
Every time it will stall with reaction run -p 8080
, and every time it'll run with meteor run -p 8080
.
With the PORT
env var set, reaction run
and meteor run
both run the server on port 3000 still for me.
I added the link to the C9 Workspace in the original post.
I can't reproduce this anywhere else, so I have to assume this is isolated to Cloud 9. I'm going to close this issue for now, but feel free to reopen it if you feel there's an issue with reaction-cli
that's responsible for your problem.
Alright sounds good. I think it happened again when SSH'ing into a Google Compute Engine server but I'll double check and comment here if so. Cheers.
I have the same problem... did you find a solution? @mikeumus
When I run
reaction run -p 8080
in Cloud 9 IDE it stalls the terminal. ThePORT
meteor env var is set. However,meteor run -p 8080
does startup the Reaction Commerce dev server successfully.Not sure if this is just a Cloud9 issue. If it is feel free to close it until more protesters arrive but just mainly wanted to report on it for now. Cheers.
Note* This is on a Pro C9 account with 2.5gb of RAM: