go-datastore requires a supported release of Go.
go get -u github.com/mrz1836/go-datastore
View the generated documentation
Database model assumptions:
idIf a unique ID is needed, the datastore expects
_idinternally for Mongo
metadatais an optional field for storing
Custom array and object fields:
WithCustomFields(arrayFields, objectFields )Use this method to add custom array or object fields (IE: metadata)
Custom methods for Mongo:
WithCustomMongoConditionProcessor()Use this method to add custom condition processing for custom object fields
WithCustomMongoIndexer()Use this method to add custom mongo indexes
This repository was created using MrZ’s
- Continuous integration via GitHub Actions
- Build automation via Make
- Dependency management using Go Modules
- Code formatting using gofumpt and linting with golangci-lint and yamllint
- Unit testing with testify, race detector, code coverage HTML report and Codecov report
- Releasing using GoReleaser on new Tag
- Dependency scanning and updating thanks to Dependabot and Nancy
- Security code analysis using CodeQL Action
- Automatic syndication to pkg.go.dev on every release
- Generic templates for Issues and Pull Requests in GitHub
- All standard GitHub files such as
- Code ownership configuration for GitHub
- All your ignore files for vs-code, docker and git
- Automatic sync for labels into GitHub using a predefined configuration
- Built-in powerful merging rules using Mergify
- Welcome new contributors on their first Pull-Request
- Follows the standard-readme specification
- Visual Studio Code configuration with Go
- (Optional) Slack, Discord or Twitter announcements on new GitHub Releases
- (Optional) Easily add contributors in any Issue or Pull-Request
Releases are automatically created when you create a new git tag!
If you want to manually make releases, please install GoReleaser:
goreleaser for easy binary or library deployment to GitHub and can be installed:
- using make:
- using brew:
brew install goreleaser
Automatic Releases on Tag Creation (recommended)
Automatic releases via GitHub Actions from creating a new tag:
make tag version=1.2.3
Manual Releases (optional)
make release-snap to create a snapshot version of the release, and finally
make release to ship to production (manually).
List of all current commands:
all Runs multiple commands clean Remove previous builds and any cached data clean-mods Remove all the Go mod cache coverage Shows the test coverage diff Show the git diff generate Runs the go generate command in the base of the repo godocs Sync the latest tag with GoDocs help Show this help message install Install the application install-all-contributors Installs all contributors locally install-go Install the application (Using Native Go) install-releaser Install the GoReleaser application lint Run the golangci-lint application (install if not found) release Full production release (creates release in GitHub) release Runs common.release then runs godocs release-snap Test the full release (build binaries) release-test Full production test release (everything except deploy) replace-version Replaces the version in HTML/JS (pre-deploy) tag Generate a new tag and push (tag version=0.0.0) tag-remove Remove a tag if found (tag-remove version=0.0.0) tag-update Update an existing tag to current commit (tag-update version=0.0.0) test Runs lint and ALL tests test-ci Runs all tests via CI (exports coverage) test-ci-no-race Runs all tests via CI (no race) (exports coverage) test-ci-short Runs unit tests via CI (exports coverage) test-no-lint Runs just tests test-short Runs vet, lint and tests (excludes integration tests) test-unit Runs tests and outputs coverage uninstall Uninstall the application (and remove files) update-contributors Regenerates the contributors html/list update-linter Update the golangci-lint package (macOS only) vet Run the Go vet application
Examples & Tests
Run all tests (including integration tests)
Run tests (excluding integration tests)
Run the Go benchmarks:
Read more about this Go project’s code standards.
Checkout all the examples!
How can I help?
All kinds of contributions are welcome 🙌! The most basic way to show your support is to star 🌟 the project, or to raise issues 💬. You can also support this project by becoming a sponsor on GitHub 👏 or by making a bitcoin donation to ensure this journey continues indefinitely! 🚀
Thank you to these wonderful people (emoji key):
|Mr. Z🚇 💻 🚧 🛡️||Siggi🚇 💻 🛡️|
This project follows the all-contributors specification.