v1.12.3
·
89 commits
to main
since this release
Highlights
- Added DB_URI support for SQL database connections in c5c750b
- Added REDIS_URI support for Redis connections in 0439ac9
- Updated several dependencies, including security-related upstream packages
- chore(deps): bump github.com/pilinux/argon2 from 0.23.0 to 0.24.0 by @dependabot[bot] in #393
- chore(deps): bump github.com/pilinux/twofactor from 1.1.12 to 1.1.13 by @dependabot[bot] in #394
- chore(deps): bump github.com/pilinux/crypt from 0.0.18 to 0.0.19 by @dependabot[bot] in #392
- chore(deps): bump golang.org/x/crypto from 0.51.0 to 0.52.0 by @dependabot[bot] in #395
- Improved GitHub issue and PR templates for clearer contributor reports in ca00e66
What changed
SQL connection URI support
You can now configure SQL connections with a single DB_URI value.
Behavior:
- If DB_URI is set, gorest uses it directly.
- If DB_URI is empty, gorest keeps using the existing field-based settings such as DBHOST, DBPORT, DBNAME, DBUSER, and DBPASS.
Supported drivers:
- mysql
- postgres
- sqlite3
Examples:
DB_URI=postgresql://user:password@host:port/db?sslmode=require&channel_binding=require
Why this matters:
- Easier deployment on platforms that provide a single database URL
- Simpler container and cloud configuration
- Better compatibility with managed database providers
Redis connection URI support
You can now configure Redis with REDIS_URI.
Behavior:
- If REDIS_URI is set, gorest uses it directly.
- If REDIS_URI is empty, gorest falls back to REDISHOST and REDISPORT.
Example:
REDIS_URI=redis://user:password@host:port
Why this matters:
- Easier integration with hosted Redis services
- Cleaner production configuration
- Less manual env assembly
Compatibility
This release is backward-compatible.
Existing setups that use:
- DBHOST, DBPORT, DBNAME, DBUSER, DBPASS
- REDISHOST, REDISPORT
will continue to work unless you choose to adopt DB_URI or REDIS_URI.
Full Changelog: v1.12.2...v1.12.3
Contributors
dependabot