The linked project includes CI and a Dockerfile for a sample app that uses SQLProvider.
Proposed Changes
The lack of guidelines on how to build and deploy a project w/ SQLProvider has delayed my team from taking SQLProvider to production. We have documented our solution on a sample repo, and we think the community could benefit from it.
Types of changes
What types of changes does your code introduce to SQLProvider?
Put an x in the boxes that apply
[ ] Bugfix (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 not work as expected)
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
[x] Build and tests pass locally
[ ] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[x] I have added necessary documentation (if appropriate)
Thanks for the PR and sorry for not merging it, but the statement that "you will need a working database connection" is simply not true. There are multiple options to do CI:
The linked project includes CI and a Dockerfile for a sample app that uses SQLProvider.
Proposed Changes
The lack of guidelines on how to build and deploy a project w/ SQLProvider has delayed my team from taking SQLProvider to production. We have documented our solution on a sample repo, and we think the community could benefit from it.
Types of changes
What types of changes does your code introduce to SQLProvider? Put an
x
in the boxes that applyChecklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.