I ran into dependency issues with jetty and datomic and finally found https://stackoverflow.com/questions/43291069/lein-ring-server-headless-fails-when-including-datomic-dependency...

that SO thread suggests http-kit but someone later says the issue returned with datomic client pro...

any suggestions for a strategy or workaround?

I'm not planning on putting this in AWS, btw, in case that's a solution (though in those docs I saw a mention of a related issue).

jetty and compojure are basic staples for me but I'm open to new things if that solves this problem. Trying to use datomic but this is definitely a blocker so far.

@macrobartfast literally the three messages above your own contain the solution i found, and that worked for juliobarros 🙂

Entity docs seem broken: https://docs.datomic.com/javadoc/datomic/Entity.html

Is it possible to use datomic-pro w/ tools.deps.alpha? I'm not seeing a way to put maven repo credentials in the deps.edn file.

Not at the moment

There is a ticket with some work on this

@robert-stuttaford holy smokes... re: the messages before mine: face palm... I should probably read a bit of the channel for the day before posting a question! Thanks... I look through those.

hi, I have an ident that i want to make unique. So far I have been getting away with always adding to my schema without breaking anything so that I can run new migrations against the production db. I'm trying to avoid any fancy tooling as long as possible. In this case I need to change an existing ident. What is the simplest way to do that? Do I need to retract the non-unique ident and then add the unique one?