Question 1

How to set up Joplin for multiple databases?

Accepted Answer

Define a configuration map in an EDN file with :databases, :migrators, :seeds, and :environments keys, then use plugins for each datastore and combine them in environment sections. Load it via joplin.repl/load-config for execution.

Question 2

Joplin vs Flyway for Clojure projects?

Accepted Answer

Joplin is better for multi-datastore Clojure projects with its extensible plugin system and native REPL integration, while Flyway is SQL-focused and might be simpler for pure SQL migrations without Clojure tooling.

Question 3

How to handle secrets like passwords in Joplin config?

Accepted Answer

Use the tagged literals #env and #envf in the EDN file to inject environment variables, as shown in the README. This keeps credentials out of source control by reading them from the runtime environment.

Question 4

Can Joplin work with MongoDB?

Accepted Answer

Yes, but through a community plugin, joplin.mongodb, which is listed separately and not part of the core library. You'll need to add it as a dependency and follow its specific setup instructions.

Question 5

How to rollback migrations in Joplin?

Accepted Answer

Use the rollback function from joplin.repl, specifying the database and the number of steps or migration ID to revert to. Ensure down migrations are properly defined in your migrator files to avoid issues.

Question 6

Is Joplin suitable for small projects with one database?

Accepted Answer

It can be overkill, as the configuration and plugin setup add complexity compared to simpler tools like raw Ragtime or framework-specific migrators. Consider it only if you need multi-datastore features or plan to scale.

Joplin

What is Joplin?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions