Skip to content
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

Seed file #216

Closed
samhstn opened this issue Sep 7, 2017 · 4 comments
Closed

Seed file #216

samhstn opened this issue Sep 7, 2017 · 4 comments

Comments

@samhstn
Copy link
Member

samhstn commented Sep 7, 2017

Ensure the seed file is working.
Add back in how to the seed file how to to run this file and what is for
Add this information to the readme

@ZooeyMiller
Copy link
Collaborator

We're looking into running the seed file, but it seems we're getting permissions issues again (using the key that you @Shouston3 gave us), and don't have the "HOOK_ENDPOINT", and can't quite see what it needs to be. Happy to update the README.md adding the relevant instructions when we've worked them out.

@finnhodgkin
Copy link
Collaborator

finnhodgkin commented Sep 7, 2017

I'm guessing the hook_endpoint is the same one I used in the hook creation script last week (https://tudo-app.herokuapp.com/api/hooks).

That portion of the seeding should already be done for all dwyl repos that @Shouston3's key has access to, so for now we could comment that section out and concentrate on the database seeding.

But yeah, it's error-ing due to bad permissions responses from the Github API so either we need to add some response handling or get a different key.

@ZooeyMiller
Copy link
Collaborator

The error turned out to be fixed by making it so that if Poison.decode is passed an empty string, we instead pass it `"{}".

I believe this is the solution @Shouston3 and @finnhodgkin came up with last week when dealing with #211.

@finnhodgkin
Copy link
Collaborator

The live version is now seeded and there are instructions in the readme 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants