-
Notifications
You must be signed in to change notification settings - Fork 400
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The explorer cannot be deployed at AWS. #17
Comments
You should be able to run the node web server on AWS, as it's basically just serving HTML. I'm not super experienced hosting with AWS but you should be able to access it on the public IP if it's running correctly. |
@mochechan you can directly deploy this on S3 bucket and use that as website. |
@mochechan I have been able to deploy the explorer project on a AWS machine successfully (although, I have a different issue at the moment). What challenge are you facing? |
what did you do? |
change the start script "http-server ./app -a localhost -p 8000 -c-1" to "http-server ./app -a 0.0.0.0 -p 8000 -c-1" in package.json |
this is a static website, if you serve the app folder it should work. there should be no need to use node to serve the explorer. |
The explorer works fine in my local machine. However, the explorer cannot work in my AWS machine.
The IP address of AWS machine is 10.10.78.X, but the machine's public IP is 52.40.25.X. It seems due to some "IP:port forwarding mechanism" I think. Is it possible to run the explorer in AWS machine? How? Thanks.
The text was updated successfully, but these errors were encountered: