Fork me on GitHub

@hiskennyness there’s also which might be useful for some use cases. I just finished moving some code I had that was using the report queue directly to a separate onyx process. Nice blog post here ( about using Datomic and Onyx

Petrus Theron15:12:51

Followed Heroku buildpack to deploy a free Datomic transactor on Heroku, but getting this error:

2017-12-30T15:30:40.144778+00:00 heroku[datomic.1]: State changed from starting to up
2017-12-30T15:30:41.948617+00:00 app[datomic.1]: Device "eth1" does not exist.
2017-12-30T15:30:41.963211+00:00 app[datomic.1]: sed: can't read /app/scripts/ No such file or directory
2017-12-30T15:30:41.970483+00:00 app[datomic.1]: Launching with Java options -server -Xms256m -Xmx2g  -Ddatomic.printConnectionInfo=false
2017-12-30T15:30:41.990735+00:00 app[datomic.1]: Picked up JAVA_TOOL_OPTIONS: -Xmx300m -Xss512k -Dfile.encoding=UTF-8  -Djava.rmi.server.useCodebaseOnly=true
2017-12-30T15:30:46.601471+00:00 app[datomic.1]: Critical failure, cannot continue: Error starting transactor
2017-12-30T15:30:46.602179+00:00 app[datomic.1]: java.lang.Exception: 'protocol' property not set

Petrus Theron17:12:44

Sigh, looks like "eth1" does not exist might have something to do with needing Heroku Spaces, which is only available on enterprise Heroku 🤕 lost half a day on this. Back to plain AWS