where do public files (css/images) go in a dry-web-roda flat app?
@cmrichards I'm doing some post regarding dry-web-roda http://gustavocaso.github.io/2017/05/dry-web-roda-for-rails-developers_part_i/
If you want to check I haven't got to the part of assets I plan on getting there
Yeah that's what got me interested
@cmrichards dry-web-roda doesn’t offer its own solution for that yet
You could choose to use Roda’s own assets/static file plugins if you wanted
But if you want to have a look a live production you can check berg from icelab
At Icelab we use https://github.com/icelab/icelab-assets + a class that reads a webpack-generated asset manifest file and offers access to the paths as
assets in our dry-view context object
I need to tweak that a bit and release it as a gem, but you get the idea
ok thanks. I guess intially I just want something that can serve simple static files from the filesystem
I'll look at Roda's own plugins
:+1:
Awesome
I'm not sure what the best way to add some kind of asset pipeline to a dry-web-roda app would be
I was thinking adding some configuration option to include webpack or something else
Is the asset pipeline problem solved in webpack/javascript world or would it be best using something in Ruby?
I dunno
Haven't play with it yet
Rails does so much for you that I'm not used to answering these kind of questions :-S
me too :laughing:
You’d wanna use webpack
Plus some little Ruby class to give you access to whatever webpack is building for you
I know webpack can do many things that rails does
it’s a whole different world, granted, but that’s where the front-end world has moved too
and rails has finally accepted this too
yeah
That icelab-assets project I linked to is our “asset pipeline” for all our Ruby apps now
Yes I want to have a look it more careful
Thanks for the info @timriley
I just realised we have
#or_fmap in dry-monads. Thanks @flash-gordon :pray:
haha, you're welcome @timriley :)
It’s a lovely codebase btw. I enjoyed looking over your recent changes.
thanks, I think I'll push something else soon, need to give it a try first :)
hey. I've just got an idea, that
dry-initializer and dry-struct both solve the same problem - define a list of attributes with constructor
I use
dry-initializer to define dependencies, and dry-struct to define an attributes
but now I need to define a dependency in my
Dry::Struct subclass, and I afraid two constructors won't live together
Would it possible or even desirable to use dry-view in rails?
@cmrichards I don't know :) But I'd love to hear if/how you get it to work.
Certainly dry-view brings some extra structure to the view layer. That's a benefit regardless of your web framework I think.