search

jrhorn424 / recruiter

Online recruitment software for economics experiments written with rails
MIT License
1 stars 1 forks source link

Heroku deploy works, but application is still failing #32

Closed jrhorn424 closed 10 years ago

jrhorn424 commented 10 years ago

http://recruiter-staging.herokuapp.com/

Generating a 500 response. Possibly related to delayed_job. Will investigate.

jrhorn424 commented 10 years ago

errors_-_recruiter_-_new_relic

ppodolsky commented 10 years ago

http://rocky-reaches-2395.herokuapp.com/

jrhorn424 commented 10 years ago

We already have a heroku instance at ices-recruiter-staging.herokuapp.com for staging and I have an app reserves for production as well. Did you get my message last week about the fixes?

Jeffrey Horn jeff@jrhorn.me http://hello.jrhorn.me/

On Sat, May 3, 2014, at 04:52 AM, Pasha Podolsky wrote:

Closed #32.

Reply to this email directly or view it on GitHub: https://github.com/jrhorn424/recruiter/issues/32

ppodolsky commented 10 years ago

I will use this instance for release deployment (because I will be in need of using paid add-ons, probably). I will deploy to your staging area soon.

P.S. I've dealt with CONNECT grant by myself.

ppodolsky commented 10 years ago

Generating a 500 response. Possibly related to delayed_job. Will investigate.

No. It is related to postgres adapter. I think, you should run db:migrate before you launch app:)

jrhorn424 commented 10 years ago

Could you grant me CONNECT privilege on heroku database? I won't be able to deal with your app correctly without configuring of the database in proper way.

I've confirmed that all you need is access to the heroku instance, which you should have had prior to May 4. Let me know if you need help getting started with heroku, but their docs are a great place to start. If you're trying to access the DB without using the toolchain, you can see: https://devcenter.heroku.com/articles/connecting-to-heroku-postgres-databases-from-outside-of-heroku.

jrhorn424 commented 10 years ago

I will use this instance for release deployment (because I will be in need of using paid add-ons, probably). I will deploy to your staging area soon.

If paid add-ons are needed, you can contact Stan Tsurilnikov at ICES to arrange for that. They'll probably want to transfer the instances to an ICES-controlled account.

If you look at the setup on the staging box, they all utilize the free tier for associated services. You can setup a cronjob on the box to fire every hour, which is a sneaky way to prevent your dyno from being shutdown.

ppodolsky commented 10 years ago

Thank you, it has been already done and working in a proper way

On 12 ìàÿ 2014 ã., at 23:55, Jeffrey Horn notifications@github.com wrote:

Could you grant me CONNECT privilege on heroku database? I won't be able to deal with your app correctly without configuring of the database in proper way.

I've confirmed that all you need is access to the heroku instance, which you should have had prior to May 4. Let me know if you need help getting started with heroku, but their docs are a great place to start. If you're trying to access the DB without using the toolchain, you can see: https://devcenter.heroku.com/articles/connecting-to-heroku-postgres-databases-from-outside-of-heroku. — Reply to this email directly or view it on GitHub.