possible change to guestbook.db.schema ns about luminus HOT 6 CLOSED

I'm actually in the process of changing the example for that. The io/resource-path is not a good default as you already noticed. :) I'll release a new template shortly.

from luminus.

Out of general curiosity, do you know why it would give the runtime exception after jar creation, when it would run fine from the lein ring server during development? Like some sort of underlying technical reason?

from luminus.

The problem is that the filesystem inside the jar is read only, so when you compile the resources folder into the jar the db can no longer be written to. The other problem was that the location for the db file was in the public folder, which is definitely not a good idea for an actual app.

from luminus.

I updated the docs here, they should get reflected in the site shortly, it polls github every half hour.

from luminus.

Cool! I'm looking forward to learning this framework deeply. Hopefully will contribute someday.

from luminus.

I just pushed out a new template as well, now the database file will be created at the path where the app is run. You'd probably want to specify the path explicitly for deployments, e.g.: /var/app/db. In general though, I'd recommend going with something like Postgres for real apps.

And hopefully there's not too much to learn with regards to the framework. I tried to keep the scaffolding to a minimum and avoid doing any magic in the templates. My experience building Clojure apps has been that the best approach is to pick the libraries that fit the app and wire them together explicitly in a way that fits with your project.

This is quite different from frameworks such as Rails, where a lot of things are done by convention and the framework often dictates the way you structure the application.

from luminus.