Heroku build

Open
#19 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
api, backend, cloud

Research direction

Start by comparing the deployed Heroku app at http://opendustmap.herokuapp.com/api/v1/ with the locally running API, then inspect the Heroku logs and deployment configuration. Verify the Postgres and Sendgrid integrations already mentioned and identify why the deployed endpoint returns Bad Request (400) while local execution succeeds. Done means the deployed API responds successfully and the cause is covered by a reproducible check.

Written by the indexing model from the issue text.

Description

After successful build and deploys to heroku, the app fails and returns Bad Request (400): http://opendustmap.herokuapp.com/api/v1/.

Postgres and Sendgrid seem to be hooked up fine. No obvious errors in logs. When building and running locally is successful and does not return bad request.

@scisco just added you to the opendustmap heroku app as a collaborator. Have any insight into what might be missing here that is causing the error?

Dominant language
Python
Stars
6
Forks
7
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from developmentseed/dustduino-server

All issues in developmentseed/dustduino-server

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.