is there a documentation on datomic reader macros? #db/fn, #datom, etc

@poernahi It's documented in d/function

thanks!

i'm thinking about migrating datastores used to power a datomic install. has anyone else done something like this or is there documentation on how to do it with zero downtime?

i see there is a way to backup and restore, which gets most of the way there, but that would require taking the system down during the process since otherwise i'm not sure how i'd get the latest changes that happen between when the backup starts and the restore completes

and ideally i'd like to be able to run both backends side-by-side for a while so i could very performance of the new datastore in production without being fully committed to it

is there an option to launch datomic cloud from terraform?

@amarjeet is your system running with the correct AWS credentials (i.e. in a role or with ambient creds)? Is it running on an EC2 instance? If so, is it in the Datomic VPC? What security group?

yes, those things seem fine. My datomic-socks-proxy consol prints this debug1: channel 2: free: direct-tcpip: listening port 8182 for entry.<system-name>.<region>. port 8182, connect from ::1 port xxxxx to ::1 port 8182, nchannels 3

and this command curl -x .$DATOMIC_SYSTEM.$ also prints {:s3-auth-path <bucket-name>}

you’re running with a socks proxy or you’re running on AWS?

your client application that is

So, while launching datomic cloud, I used socks proxy process

Now, I have a pedestal app, that I want to connect with that cloud db

right. and where is your pedestal app running?

its my local system

ok. your cfg map doesn’t specify the proxy-port

https://docs.datomic.com/cloud/getting-started/connecting.html#use-datomic

when you’re running locally through the socks proxy you need to include the :proxy-port in your cfg map

okay, so when I specify the port as 8182, I get connect refused error

just a sec

m checking again

your pedestal app (however you’re launching it) will also need to be running with ambient AWS credentials

Unable to connect to system: #:cognitect.anomalies{:category :cognitect.anomalies/unavailable, :message "Total timeout 60000 ms elapsed"} thsi is the erro I am getting with proxy-port

aws creds mean, I should put the credentials in project.clj as {:user {:aws ...}}

much better to put them in the ambient environment via standard AWS env vars

i don’t know about lein specifically; i usually use the ambient env creds

yeah, what @alexmiller said

don’t check your aws creds into your git :)

https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html#cli-quick-configuration

okay 🙂 let me try this. I am pretty much newbie to the deployment side of things

aah, its connected now

thanks much both of you 🙂

np

does the datomic-pro peer server allows backups? we run datomic.peer-server on localhost: Serving datomic:<mem://hello> and then try a backup but keep getting Invalid database URI errors

you can’t run a backup of a mem database

backup and restore require storage

got it -- thanks... we ultimately plan to run on AWS but want to understand backup/restore before we push there

see https://docs.datomic.com/on-prem/backup.html#sec-8

you can run a local transactor with a dev database and use both peer-server against it as well as backup and restore

see https://docs.datomic.com/on-prem/dev-setup.html

thanks @marshall, we'll keep reading...

When using Dynamo as the storage backend, is it safe to rely on Dynamo snapshots for backup, or should we still be using Datomic’s backup tool?

You should use datomic backup

https://docs.datomic.com/on-prem/ha.html#use-datomic-backup

Ddb snapshots don't provide the required semantics for a consistent copy of a datomic db