roterski.fulcro.rad.database-adapters.crux.start-databases — net.clojars.roterski/fulcro-rad-crux 0.0.1-alpha-1

start-database! clj

(start-database! config opts)

Starts a Crux database node given the standard sub-element config described in start-databases. Typically use that function instead of this one.

• :config a crux config map passed directly to crux.api/start-node. See the documentation https://opencrux.com/reference/21.02-1.15.0/configuration.html

Returns a migrated database connection.

start-databases clj

(start-databases config)

(start-databases config options)

Start all of the databases described in config, using the schemas defined in schemas.

• config: a map that contains the key co/databases.

The co/databases entry in the config is a map with the following form:

{:production-shard-1 {:crux.jdbc/connection-pool {:dialect #:crux{:module "crux.jdbc.psql/->dialect"}
                                                 :db-spec {:dbname   "fulcro-rad-demo"
                                                           :user     "postgres"
                                                           :password "postgres"}}
                     :crux/tx-log               {:crux/module "crux.jdbc/->tx-log"
                                                 :connection-pool :crux.jdbc/connection-pool}
                     :crux/document-store       {:crux/module "crux.jdbc/->document-store"
                                                 :connection-pool :crux.jdbc/connection-pool}}}

where the key (i.e. :production-shard-1) is a database name and the value is a crux config map passed directly to crux.api/start-node. See the documentation https://opencrux.com/reference/21.02-1.15.0/configuration.html

NOTE: crux expects the value under :crux/module key to be a symbol so if you want store the config in edn file, you can use strings for :crux/module values and pass the config through symbolize-crux-modules before calling start-databases:

(require '[roterski.fulcro.rad.database-adapters.crux :as crux])
(crux/start-databases (crux/symbolize-crux-modules config))

• options: a map that contains co/transaction-functions

Each supported driver type has custom options for configuring it. See Fulcro's config file support for a good method of defining these in EDN config files for use in development and production environments.

Returns a map whose keys are the database keys (i.e. :production-shard-1) and whose values are the live database connection.

transaction-functions->txs clj

(transaction-functions->txs t-fns)