Closed ohnorobo closed 11 years ago
Additional note: when geolocation fails search loads just fine.
Looks like you're using a different AWS setup than the one I spun up. I don't mind taking a look if you give me access; also, if you're no longer using the one I spun up let me know so I can terminate it.
@JBaldachino I can add you tonight, I think. Also, is it worth taking a look at OpenShift for hosting? More trouble than it's worth?
I'm most comfortable with AWS (I've been administering servers on there for the past two years). I don't see anything in our stack here that would give me any headaches for now.
If someone wants to play with a hosting service like OpenShift now, don't let me stand in your way! If it were up to me I'd stay in AWS for now and when we're more production ready we'll worry about where exactly we want to host it.
Working now.
@ohnorobo I made some recent commits to search, I'm not sure if those had anything to do with it, or if it had more to do with changes that @JBaldachino was able to make.
Problem with current ec2 setup.
Search failing with 500 Something about query params is causing the search route to fail
GET http://ec2-67-202-32-253.compute-1.amazonaws.com/search?location%5Bspeed%5D=&location%5Bheading%5D=&location%5BaltitudeAccuracy%5D=&location%5Baccuracy%5D=26&location%5Baltitude%5D=&location%5Blongitude%5D=-71.1011206&location%5Blatitude%5D=42.3271702&radius=5 500 (Internal Server Error) jquery.min.js:6 {"error":{"message":"Maximumcallstacksizeexceeded"}}
search with no params works fine, and running locally works fine.