announcements

Project/library announcements ONLY - use threaded replies for discussions. Do not cross post here from other channels. Consider #events or #news-and-articles for other announcements.
2021-04-23T06:16:09.021300Z

Hi, nice work 👍 @karol.wojcik if anything is needed just ping me

Karol Wójcik 2021-04-23T06:16:49.022100Z

@dainius.jocas 1.Would love to know whether you pay anything for hosting the layer? 2. May I please tag you in the repo for the parts that were inspired by your work?

2021-04-23T06:23:55.022600Z

1. The layer was uploaded using my personal AWS account but to have the layer uploaded I didn't have to pay. AFAIK, you pay just for the usage of lambdas that uses some layer, i.e. the regular AWS price. 2. Yes, that would be great. I'm curious to learn which parts of my little hack helped others @karol.wojcik

Karol Wójcik 2021-04-23T06:24:53.022800Z

1. So each time somebody use my layer I pay for it?

2021-04-23T06:30:13.023Z

No. The lambda layer is like the library in clojars: you just upload it (free for you), and whoever use it in whatever way they do it, you have nothing to do with paying anything. Another way to think that a layer is just a zip in some public AWS S3 bucket, i.e. you pay nothing, and you aren't paid.

Karol Wójcik 2021-04-23T06:37:24.023200Z

Ok got it. That was exactly the part I was missing. Thank you so much.

2021-04-23T20:05:02.029700Z

Hi everyone! I’ve written https://github.com/prestancedesign/inertia-clojure a Ring middleware for https://inertiajs.com/, a new concept to build single-page apps without building an API. This lets you build SPA with Reagent, React, Vue and Svelte using Clojure server side for the routing, controllers, etc. If your interested, there is some examples in the lib repo: https://github.com/prestancedesign/inertia-clojure Cheers!

5👏116👀
2021-04-24T13:54:32.032700Z

Woohoo! My Clojure adapter is added to the Inertia website. 👍

4👍
2021-04-25T15:11:56.051300Z

I started embarking on a project creating a ring-like interface for express. It’s working but want to think some things through and write docs/tests before releasing. How true to ring’s API did you stay? Right now all my test handlers are manually extracting promise data that the request could be wrapped in and returning a promise with the result. I’m tempted to switch gears to something between ring and interceptor based since I can manage promises automatically between the handlers that way. Given that you made this I might go ahead and change my api so that it’s ring-ish but is async or sync without the user having to think or know about it.

2021-04-27T20:08:08.079700Z

Sound interesting. 👍 It kinds remind me Macchiato, do you know? https://github.com/macchiato-framework/macchiato-core

2021-04-28T04:28:14.090600Z

I had no idea about that one. Thanks! It's definitely higher quality than what I have currently. Might expand on what I have to make it more ergonomic for cljs\js and see what comes of it. Will definitely have to start playing with your library and macchiato though 🙂

1👍