Oracle Support in drm-cli v1.1 #7
dband-drm
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We've been getting questions about Oracle support since the v1.1 announcement, so this week we're digging into it properly.
Oracle deployments have a reputation — deservedly — for being painful. The tooling is fragmented, the licensing is expensive, and the gap between "we have Liquibase or Flyway set up" and "we have a repeatable, audited release process" is wider than it should be.
drm-cli v1.1 adds Oracle to the list of supported databases, sitting on top of Liquibase or Flyway (whichever you're already using), and giving you the same release management layer we've had for SQL Server from the start:
This week on the blog
We published a full step-by-step tutorial on dev.to:
→ Deploy to Oracle with drm-cli + Flyway: No Enterprise License Required
It covers:
solution.yamlfor a Flyway-backed Oracle deploymentdrm-cli encryptDiscussion prompts
We're genuinely curious about your Oracle setups. A few questions:
Drop your thoughts below. We read everything and respond to every comment.
Quick links
drm-cli is free and open-source. No license cost, no freemium tier, no enterprise edition. If it's useful to you, a ⭐ on the repo helps more people find it.
Beta Was this translation helpful? Give feedback.
All reactions