joplin.crux

[joplin.crux "0.0.1-SNAPSHOT"]

Usage - Clojure

You can use the joplin.repl namespace from within Clojure itself. In these examples:

• config is an example joplin config (EDN)
• :prod is an example environment
• :crux-prod is an example database

(joplin.repl/migrate config :prod)
(joplin.repl/rollback config :prod :crux-prod 1)
;; or (joplin.repl/rollback config :prod :crux-prod 20151215114952-users)
(joplin.repl/seed config :prod)
(joplin.repl/reset config :prod :crux-prod)
(joplin.repl/pending config :prod :crux-prod)

Usage - Command Line

You can run a lein alias from the command line if you configure them in your project.clj, like so:

:aliases {"migrate"  ["run" "-m" "joplin.crux.alias/migrate"  "joplin/config.edn"]
          "seed"     ["run" "-m" "joplin.crux.alias/seed"     "joplin/config.edn"]
          "rollback" ["run" "-m" "joplin.crux.alias/rollback" "joplin/config.edn"]
          "reset"    ["run" "-m" "joplin.crux.alias/reset"    "joplin/config.edn"]
          "pending"  ["run" "-m" "joplin.crux.alias/pending"  "joplin/config.edn"]
          "create"   ["run" "-m" "joplin.crux.alias/create"   "joplin/config.edn"]}

Then you can run Joplin commands from the command line:

lein migrate prod
lein rollback prod crux-prod 1
# or lein rollback prod crux-prod 20151215114952-users
lein seed prod
lein reset prod crux-prod
lein pending prod crux-prod

NOTE: You must refer to the joplin.crux.alias shim in your aliases, unlike the default alias configuration seen in the joplin.core example.. Because joplin.crux is a plugin, joplin.alias doesn't know about it out of the box. This is arguably a bug in Joplin.

Generate Migrations

(joplin.repl/create config :prod :crux-prod "add_users_schema")

or

lein create prod crux-prod add_users_schema

Additional Documentation

• Using Joplin (including a config example)
• Joplin Example Project
• Joplin Example REPL Usage
• Joplin Example project.clj

TODO

• It was suggested by @jarohen that joplin.crux could use Transaction Functions to ensure that all migrations executed at once share the same tx-time. This will definitely make the historical timeline for schema and data migrations cleaner, but it also requires a "meta schema change" of sorts, which is the Transaction Function itself. I'm a bit nervous making any assumptions about what sort of entities the consumers of joplin.crux want in their database, so I've left the direct (naive) implementation for now. This upgrade can always come later without impacting historical migrations.

Developing

Run tests:

lein test

License

Copyright © 2021 Pariyatti

Distributed under either the MIT License or the Eclipse Public License (1.0 or later).