lib-onyx.joplin

Liking cljdoc? Tell your friends :D

Clojure only.

get-task-map-lifecycle-config
joplin-migrations
JoplinConfigSchema
JoplinDatabaseDescriptor
no-pending-migrations?
supported-plugins
with-joplin-migrations

get-task-map-lifecycle-config^clj

(get-task-map-lifecycle-config lifecycle event k)

Tries to get a piece of data in the task map or lifecycle

Tries to get a piece of data in the task map or lifecycle

source raw docstring

no-pending-migrations?^clj

(no-pending-migrations? event lifecycle)

source

supported-plugins^clj

source

with-joplin-migrations^clj

(with-joplin-migrations)

(with-joplin-migrations joplin-environment)

(with-joplin-migrations joplin-environment joplin-config)

This task bundle modifier will continously try to apply data migrations before allowing the task to start.

joplin-config structure can be discovered from the schema and is specific to your database(s). It is generally of this structure

{:environments {:dev [{:db {:type :sql :url 'jdbc-url'} :migrator 'resources/migrators/sql'}]}}

joplin-environment is a selector for a specific config. The only valid selector for the above example would be ':dev'.

The datastructure is expected in this form to make interop with the joplin command line tools simple, since they share an expected shape. More can be read about Joplin here https://github.com/juxt/joplin.

If you are providing this config data another way, either manually or through a seperate mechanism, you may elide either-or the joplin-config or joplin-environment.

This does not apply data seeders.

This task bundle modifier will continously try to apply data migrations
before allowing the task to start.

- joplin-config structure can be discovered from the schema and is specific
to your database(s). It is generally of this structure

{:environments {:dev [{:db {:type :sql
                            :url 'jdbc-url'}
                       :migrator 'resources/migrators/sql'}]}}

- joplin-environment is a selector for a specific config.
The only valid selector for the above example would be ':dev'.

The datastructure is expected in this form to make interop with the joplin
command line tools simple, since they share an expected shape. More can be
read about Joplin here https://github.com/juxt/joplin.

If you are providing this config data another way, either manually or through
a seperate mechanism, you may elide either-or the joplin-config or
joplin-environment.

This does not apply data seeders.

source raw docstring