Closed hamza-sondermarketing closed 4 years ago
@tongueroo This is kind of an urgent issue that needs to be fix. Can you help me out here. I have checked and verified my DATABASE_URL
on local and it is connecting and working fine.
I really don't understand where the issue is as cloudwatch is not telling me any issue.
@hamza-sondermarketing This is not urgent. It's a demo app.
This is more of a usage question. Please review the issue guidelines again. Like these other issues: #456 #460 #463 Keeping questions on the forum helps keep the signal-to-noise ratio higher.
Responded to the community post with some tips: https://community.rubyonjets.com/t/could-not-find-a-javascript-runtime-see-https-github-com-rails-execjs-for-a-list-of-available-runtimes-execjs-runtimeunavailable/440
Checklist
jets upgrade
command that makes this a simple task. There's also an Upgrading Guide: http://rubyonjets.com/docs/upgrading/My Environment
Expected Behaviour
I have followed jets-afterburner-serverless-rails-on-aws-lambda-in-5-minutes and try to deploy the demo rails application with
jets deploy
command. Every thing seems to work as I don't get any error in the cloudwatch logs but upon hitting the endpoint returned from the after deploy command, it should load the demo rails site.Current Behavior
After hitting the Endpoint
https://lo4lne31h5.execute-api.us-east-1.amazonaws.com/dev/
, instead of loading the content, it displays the following message:CloudWatch Logs
Code Sample
I have used the existing demo-rails repo in my project and code can be found here: my-rails-demo-app
Solution Suggestion
I have shared the logs above and found no issues, but still it is timeout. No idea whats going on here. Kindly suggest.