There are two tests.py?

Bug: Zeit doesn't appear to support MySQL databases or any for the time being. (which breaks the example)

Request: Need to set up a firebase example so that there is some sort of queryable version of an endpoint.

Working with and Submitting Issues

Existing Issues

When working with existing issues, you will need to keep a clear line of comments detailing what you are working on and how you plan to address the current issue.

If you are doing a PR or any commits, please make sure to reference the issue number in the respective commit or PR.

New Issues

When submitting a new issue, your headline should contain the following:

Issue Type: Issue Title

Example titles:

BUG: Routes don't work with Heroku

FEATURE: Add Heroku install script

For the issue body, your template will vary.

BUGS

Please use the following template:

### Prerequisites

* [ ] Can you reproduce the problem in safe mode?
* [ ] Are you running the latest version?
* [ ] Did you check the debugging guide?
* [ ] Did you check the FAQs on Discuss?
* [ ] Are you reporting to the correct repository?
* [ ] Did you perform a cursory search?

For more information, see the `CONTRIBUTING` guide.

### Description

[Description of the bug or feature]

### Steps to Reproduce

1. [First Step]
2. [Second Step]
3. [and so on...]

**Expected behavior:** [What you expected to happen]

**Actual behavior:** [What actually happened]

### Versions

You can get this information from executing `npm version`.

Pull Requests

Please use the following template:

## Types of changes

What types of changes does your code introduce? Put an `x` in all the boxes that apply:

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
- [ ] I have read the **CONTRIBUTING** document.
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.

## Comments
Please add any comments here.

Maybe check the mac version and don't run the scrip if its not compatible?

This issue represents the tasks that we would like accomplished for the project at the current time. If we are taking control of a task, or adding one here, there should be an associated issue card to track what is being done.

• Update documentation for each of the functionalities #4
• Update bash install script for conditional logic. (Must ask if user wants a specific installer set up and respond to user input.)
• Setup boilerplate to deploy on Heroku via script #3
• Setup boilerplate to work with Netlify
• Configure Database example to work with Google Firebase database storage #2
• Configure Database example to work with AWS database storage

• Explain use of now.json (with link to zeit now docs)
• Explain folder structure (every service that should be an active route needs an index.py that will handle the view (don't use named files unless you are building static routes)

Need to prepare and test integration with heroku.

• add dependencies to install script
• add package to pipenv
• create heroku demo account
• add config
• test integration

Dynamic routing is not working when routes are not in repo root.
Tracking issue here: vercel/vercel#2685

Right now, You can declare all routes manually. The objective for this framework, however, should be to establish dynamic routes.

We should continue to track the issue listed above and update after the fix releases.

So that the repo can truly be open source, we need a contribution guide and templates for PR and Bug reports.

• Create Contribution Guide
• Integrate bot for Contributors
• Add Issue template and PR Template
• Update readme to reference contribution guide

I know we are doing microservices, but still I think all the configurations for the Flask database should be in just one place, that way we can import it and declare our models on every model.py.

The current way could lead to bugs because maybe I forget to copy and paste the configuration to every modal.py