populate subscription data for initial setup #70
Conversation
kentwills
changed the title
yelp_beans/routes/tasks.py
Outdated
|
|
||
|
|
||
| @tasks.route('/init', methods=['GET']) | ||
| def init(): |
There was a problem hiding this comment.
Are we sure this should be its own route? I feel like this is better-suited to a one-off executable that we provide.
Similar to rake db:seed that rails does
There was a problem hiding this comment.
Explored the option of using a script with the remote api. I was attempting to cut down on the user complexity of having to add remote_api: on to the app.yaml, deploying, running a script, removing the line, and deploying again.
The route is only accessible by admins and is a noop if there is data, while not great from an engineering perspective, it seems to be the quickest upstart from a user perspective.
yelp_beans/routes/tasks.py
Outdated
| @@ -92,3 +96,31 @@ def send_match_emails(): | |||
| logging.info(matches) | |||
| send_batch_meeting_confirmation_email(matches, spec) | |||
| return "OK" | |||
|
|
|||
|
|
|||
| @tasks.route('/init', methods=['GET']) | |||
There was a problem hiding this comment.
And this definitely shouldn't be a GET
|
Looking for a better route to populate starter data. |
Helps initial state for people creating the app for the first time #23