[ANN] Gimlet Cocktail 0.1.0 & Gimlet Render 0.0.1

[Harley Laue]

Gimlet Cocktail is a micro web application framework for OpenResty (or Xavante) written in Moonscript. The hope is that it's useful, modular, and makes writing web applications (especially RESTful ones) quick and fun.
https://github.com/losinggeneration/gimlet

Gimlet Render is a middleware for Gimlet Cocktail used for encoding JSON responses & handling HTML templates & layouts.
https://github.com/losinggeneration/gimlet-render

I'm pleased to announce the first official versions of Gimlet Cocktail & Gimlet Render. While I announced the project less than a month ago, this marks the first version of the project(s). It should be to the point where it's mostly feature compatible to Martini, which the project is highly based upon.

LuaRocks:
The releases can be downloaded with luarocks from the MoonRocks server (Thanks again leafo for that, Moonscript, etlua, etc, etc, etc :D)
http://rocks.moonscript.org/modules/losinggeneration

Any/all of the following are always welcome:
Feedback & questions by replying to this thread, twitter @losnggeneration, or emailing me directly.
Issues & pull requests can be done from the respective Github repositories.

[Yong Wang]

Hi Harley,

Are there any database backend support in Gimlet Cocktail?

Thanks

Yong

--
You received this message because you are subscribed to the Google Groups "MoonScript Users" group.
To post to this group, send email to moonscri...@googlegroups.com.
Visit this group at http://groups.google.com/group/moonscript-users.

[Harley Laue]

There isn't anything built-in like Lapis's database functionality. However, it should be possible to use existing database libraries. For instance, you should be able to use something like lua-rds-parser if you're using OpenResty. However, I'm not sure what specific OpenResty incompatibilities there are with trying to use, for example, LuaDBI. If you use Xavante, I would think these libraries should work fine. Another possibility might be to *borrow* Lapis's database code (while trying to rip out the Lapis specific pieces, like lapis.config.) This may or may not be a big task.

In any case, this is likely my next area to focus on. At the very least, figuring out exactly what is and isn't going to work to document within the README. I doubt there will every be anything ORM-like directly supported. It could be a separate project, because you likely just need to setup the connection and map the table to be passed to the requests.