Explain/Create Initial Database State for New Projects

[kentwills]

For those unfamiliar with Google App Engine, there is a bit of a hurdle to go from the current project to something that can be used quickly. All database manipulations happen through the App Engine Datastore portal. We should either give a quick tutorial for initial state or provide a script to populate initial state.

[elg0nz]

Any updates on adding these instruction? I've managed to build and push the app to Google App Engine. But even after updating the employees json and running the populate_employees task, I only see the Darwin Yelp user.

Also whenever I try to make a new meeting request, I get back a 500 error. I'll be happy to help writing a bootstrapping script if you can provide a "SQL dump" or equivalent of the desired initial state.

[kentwills]

@elg0nz It's great to hear that you got the application up and running. I set up a slack channel @ yelp-beans.slack.com where we can help you work through individual problems with stack traces. Maybe we can work through your problem specifically and see what patches / additions to documentation we should add?

[elg0nz]

Sounds great, could you send me an invite to the email on my profile? (@elg0nz) Cheers!

[kentwills]

sent!

[bxm156]

@kentwills Should we make that slack channel public?

@elg0nz You will only see your user on the homepage. Did you authorize the application with the same google email that matches your employee record that is in the employees.json file?

[elg0nz]

@bxm156 Kent and were looking into this issue this morning, and this is what we came up with:

In order for a user to be displayed & able to request a meeting the following must happen:

1. The employee row from the JSON dict must include a location param. i.e. {"first_name": "Bob", "last_name": "Foobar", "metadata": {"location": "somewhere"}, "photo_url": "http://s3-media4.fl.yelpcdn.com/assets/srv0/yelp_large_assets/3f74899c069c/assets/img/illustrations/mascots/[email protected]"}
2. The following entities must be populated: Rule, MeetingSubscription, DateTimeSubscription

[kentwills]

@bxm156 @elg0nz to clarify on the point above, the requirement is only to have a location param because the rule was set to look at location.

This highlights that rules are required. Without them being added to a subscription, the user will not see the subscription (it's a whitelist). Maybe this shouldn't be the default?

[carnalim]

Looking through this project do you mind adding my email on my profile as well. The directions are not that intuitive, I just picked up google cloud for this project and am combing through any documentation and issues but there is almost nothing to go off of.

[kentwills]

@carnalim Added! Yeah this is pretty tough right now because you have to be familiar with the ecosystem and know what the app expects. We just simplified this by one step, removing the need for rules for a subscription. To update the database, everything is done through the datastore in appengine at the moment. I would like to see a script that people can run to get people started.