There are many advantages to this, including being able to generate the admin and api automatically, (as well as letting our frontend guys add properties they need in a model without pestering the backend guys to make schema updates!). If manipulating schemas through the admin makes you nervous, you can always write migrations for your model changes: http://caribou.github.io/caribou/docs/migrations.html
By the way the documentation is great. You guys nailed it! Bonus points for having a philosophy! :-)
--
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clo...@googlegroups.com
Note that posts from new members are moderated - please be patient with your first post.
To unsubscribe from this group, send email to
clojure+u...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to a topic in the Google Groups "Clojure" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/clojure/KeyaMJERW0o/unsubscribe.
To unsubscribe from this group and all its topics, send an email to clojure+u...@googlegroups.com.
--
Ryan - that is great news. Are we allowed to know what else will be release :-).
Justin,As far as I know, Immutant is not a dependency, but an option. Let me know if that is not true however.
On Tuesday, November 12, 2013 10:13:17 PM UTC-8, Justin Smith wrote:Typically my first step making a caribou app is to remove the immutant dependency. It's pretty straightforward to take it out.
On Tuesday, November 12, 2013 9:19:27 PM UTC-8, Prasanna Gautam wrote:This is really cool. Very easy to get up and running for first try. I have a few questions on the architecture.Why Immutant instead of plain ring as the default? I think the number of dependencies could be much lower with it.I know it's only alpha.. but I'm asking this on behalf of others who might be thinking the same.And, are there plans for NoSQL database support, like MongoDB, MapDB (http://www.mapdb.org/ - I just found out about it myself but this is the only decent in-memory NoSQL solution other than Berkeley DB)?
On Tuesday, November 12, 2013 6:52:10 PM UTC-5, Ryan Spangler wrote:Hello Clojure,Excited to announce today the release of Caribou! http://let-caribou.in/We have been building web sites and web applications with it for over two years now and improving it every day. Currently we have four people working on it and another ten using it to build things, so it is getting a lot of real world testing.It has been designed as a collection of independent libraries that could each be useful on their own, but which come together as a meaningful whole.We have been spending the last couple months getting it ready for a full open source release, and I am happy to say it is finally ready. Funded and supported by Instrument in Portland, OR: http://weareinstrument.com/ We have four projects using it in production, and several more about to be launched (as well as over a dozen internal things).Documentation is here: http://caribou.github.io/caribou/docs/outline.htmlSource is here: http://github.com/caribou/caribou (use this for issues, you don't actually need the source as it is installed through a lein template).Some of the independently useful libraries Caribou is built on are:* Polaris -- Routing with data (not macros) and reverse routing! : https://github.com/caribou/polaris* Lichen -- Image resizing to and from s3 or on disk: https://github.com/caribou/lichen* Schmetterling -- Debugging Clojure processes from the browser: https://github.com/prismofeverything/schmetterling* Antlers -- Useful extensions to mustache templating (helpers and blocks, among other things): https://github.com/caribou/antlers* Groundhog -- Replay http requests: https://github.com/noisesmith/groundhog
And many others.Basically this is an Alpha release, and I am announcing it here first in order to get as much feedback from the community as possible. We have made it as useful as we can for our purposes and recognize that for it to improve from here, we really need as many people using it and building things with it as possible. The documentation also needs to be put through its paces: we need to see how well people are able to use it who know nothing about it, based only on the existing docs.All feedback welcome!Thanks for reading! I hope you find it useful.
--
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clo...@googlegroups.com
Note that posts from new members are moderated - please be patient with your first post.
To unsubscribe from this group, send email to
clojure+u...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups "Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clojure+u...@googlegroups.com.
You received this message because you are subscribed to a topic in the Google Groups "Clojure" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/clojure/KeyaMJERW0o/unsubscribe.
To unsubscribe from this group and all its topics, send an email to clojure+u...@googlegroups.com.