Thank you for doing this service! I understand purge just uses a regex to remove unused classes. Do you have suggestions on what the regex will look like if you use purge?

if you are going to setup a CSS processing pipeline, its probably better to stick with the official Tailwind build, specially with their new JIT thing, which is awesome 🙂 the target audience of this garden versions is for people that don’t want to mess with more node things

that said, I think would be the same thing, that depends more on what you are using to write the HTML. If using hiccup for example, something like :div.text-sm.bg-gray-400 may not work by default, but if you use [:div {:class "text-sm bg-gray-400"} it probably works out of the box

Wow, I just saw the JIT thing, will have to check how that can be leveraged. What I'm missing in CLJS with tailwind is autocomplete and purge (since the raw size is huge). But I think your tailwind-garden will give me more ideas.

there is this example configuration for tailwind jit with shadow: https://github.com/jacekschae/shadow-cljs-tailwindcss

Thanks a lot, will check this one out 🙂

@UMPJRJU9E purge works fine for me in CLJS, for both hiccup notations

with the default setup from tailwind docs; IIRC it’s only triggered on release build, so beware to check bundle size diff against that

Looks really cool! I made an attempt at something very similar a while back https://github.com/lukaszkorecki/taskmaster

Super cool! I was just looking for something like this a month ago… I ended up putting the project on hold so didn’t make a choice, but I was thinking of trying https://contribsys.com/faktory/ with https://github.com/apa512/clj-faktory. This is now bookmarked for next time I need something similar.

@U06BEJGKD Kudos on the clear and comprehensive docs. Takes a lot of effort, and well worth it.

Also I like how it’s flexible enough to run the workers in the same VM as the rest of an app (e.g. a Web app/server) or in one or more discrete/dedicated VMs. Very nice!

@U69US348Z Thanks! Yeah, I’ve put some effort into the documentation. It really helps with the design process too, writing down how it’s supposed to work. Hope it can be helpful to you in the future!

> It really helps with the design process too, writing down how it’s supposed to work. +1000000

Cool name

Long ago, the four nations lived together in harmony...

I think it’s interesting how we have different use cases. For instance, I wouldn’t use Asami for high speed small transactions (especially on disk!) but it’s good for querying

Also, being schema-less can be far more convenient (e.g. you can just load arbitrary JSON into it, and it automatically turns it into a graph). But this has implications for upsert

I just have to wonder… which project is the Fire Nation?