@bradford for the route syntax you're using you need

["/echo"
  ^:interceptors [(b/body-params)] 
  {:post test-channel}]

Is it better to ask Vase questions in the #vase channel (which seems to be very quiet) or here?

Hmm, LOL, looks like that channel has only two subscribers (including me). So, repeating question here:

I'm trying to run the petstore-full sample (https://github.com/cognitect-labs/vase/tree/master/samples/petstore-full) but I'm getting an error Connection Refused localhost:4335

I did git clone & lein install & cd samples/petstore-full/ & lein run

Hmm, I'm guessing that I need to start Datomic, but how?

@deg

you can quick start that vase example by replacing datomic uri from :datomic-uri "datomic:" to :datomic-uri "datomic:" . So you don't have to setup datomic free.

Vase creates the db on startup if it doesn’t already exist

By using an in memory datomic uri, you don’t have to do any additional setup

as @nxqd stated

To use Datomic Pro and a non in-memory db, you need to startup a separate Datomic process

Thanks. I do this in all five of the .edn files?

In case you’re interested, here’s where the Datomic DB get’s initialized. https://github.com/cognitect-labs/vase/blob/master/src/com/cognitect/vase.clj#L45

@deg seems so

Thanks, that worked!

How could i have started up a separate Datomic process, if I didn't want to edit those files?

So you’d download Datomic free: https://my.datomic.com/downloads/free

Once you unzip the archive, there’s a bin dir

Thanks. And, I assume, some obvious help file inside saying what to run.

hmm, looking. Been a while since I’ve run Datomic free

should be the same as pro

Am I missing something about the Vase philosophy? The docs say that it is self-contained with Datomic enclosed. Yet, the sample app is configured to need Datomic pre-installed or undocumented changes to its config file.

Stranger, the Vase sample app mentions that changes are needed to move from Datomic Free to Pro. But, no mention of what is needed for the in-mem version that comes with Vase itself.

(Is this even the right channel for me to be venting about this? Or is there a more Vase-specific place? -- #vase seems to abandoned)

So let me make sure I’m not giving you bad advice, It’s been a while since I’ve run the vase samples.

@deg, so for now I think this is the right place for your Q’s.

re: Datomic free, it requires you to spin up a local transactor using the bin/transactor cli which is available when you download Datomic free

Vase does include Datomic free as a dependency but that’s for the peer

The Vase samples shouldn’t really depend on Datomic free. An In-memory DB would be better

I’d recommend using at least Datomic free when running a real hobbie system. For Prod I’d consider Datomic Pro.

for exploration, in memory db’s are fine

@deg There are definitely gaps in the docs that need to be closed.

Got it, thanks. I'm putting together a small PR with this and some other minor typos I found in the docs. I was going to just add to the readme, giving the change you supplied above. But, would it be better to instead change the .edn files so they work immediately?

(same effort for me; I either commit the .edns I changed or the readme I changed)

@deg I’d create a separate PR for changing the edn files to use an in memory db plus the readme update.

that would be super helpful

will do.

Time allowing, I'll review the other samples too.

Great, thanks for digging in!

Most of the other samples work as is. But, vasebi crashes on first connection to localhost:8080. I don't grok the entire stack trace, but looks like the immediate cause is an NPE.

@thegeez thanks!

@ddeaguiar Is there anyway I can help with the development of Vase somehow? It seems very interesting. I'm familiar with Clojure(script) but haven't had any experience contributing to open-source.

@alanspringfield, there sure is. There are gaps in the documentation. At minimum the creation of issues around that would be useful. There are already some issues for that as well. If you’d like to contribute to the code, be sure to check out the Contributing section of the README (https://github.com/cognitect-labs/vase#contributing).

I highly recommend creating an issue and soliciting feedback for any remotely significant change… before doing any of the work.

In any case, doc fixes are a great way to dive into open source contribution.