Is there any way to serve static files on the jvm classpath?

(yada (io/file "public")) references the file system

I'm going to say yes, I'll see if I can find the snippet

(yada (Class/getResource "resources/"))

(io/resource "resources/") may also work

I've tried the latter, doesn't work

ah.

this is the result of (yada (io/resource "resources/"))

i've only gotten (io/file ...) to work

No luck with the Class/getResource?

nope 😕

https://github.com/juxt/yada/blob/1c983d4c3c3e427fa6bfc424992d1d50bceecb4c/manuscript/010_intro.md#say-hello-to-yada But it#s in the docs!

is it under new-classpath-resource?

That looks like it should work, yep

seems like private api

https://github.com/juxt/yada/blob/fd5e17350f8f8d7a2369b173862adcd76f38c82f/dev/src/yada/dev/docsite.clj#L143

let me try getResource again

clojure.lang.ExceptionInfo: No matching method: getResource

That sounds like Class/getResource is failing, no?

I see it on the docs though

https://docs.oracle.com/javase/8/docs/api/java/lang/Class.html

hmm

(.getResources Class "path/")

It's not a static method

ah let me try that

can't really confirm that that works

Because you're on boot, like me 😛

I want yada to serve up stuff from inside the jar after uberjaring

but at the same time serve from the classpath boot set up

while doing boot dev etc

Looking at the source, @malcolmsparks may need to extend java.net.URL class to work as a resource (for io/resource), new-classpath-resource is what you're after, no doubt in my mind. It's designed for EXACTLY your need. It's really cool.

in my repl (.getResource ...) returns nil

turns out only boot.jar is in the classpath

Yeah, I assume for no resource found.

I'll jump into the edge repo and check

I was using new-file-resource last time

but malcolm told me the canonical way was to call (io/file ...)

so I'm thinking there's a better way for these classpath stuffs

I mean, this works:

(yada (io/file (io/resource "a-file-in-resources.foo")))

The reason io/resource doesn't work is because of java.net.URL vs java.io.File

there's a corresponding coercion for URL in yada

There is?

Hmm

https://github.com/juxt/yada/blob/2874ea683f7c6caf6fa0901677ad6f24a00c9450/src/yada/resources/url_resource.clj

resource works fine, but only for a single file

(yada (io/resource "file-in-classpath.foo"))

but it doesn't work for a directory

because classpath has no concept of directories

(that's what micha told me)

ah.

Interesting.

Micha is clever like that 😛

micha [11:35 AM] i guess what you need is a task that makes a manifest of all the files in public [11:35] so you can add them one by one [11:35] as yada endpoints

I'd just use new-classpath-resource 😛

so he suggested a file manifest

let me try that

Malcolm is using it for swagger & such at this point.

It'll possibly change in the future.

hmm

new-classpath-resource only allows OPTIONS

I get a 405

I guess it's not meant for that

I can make do with io/file, just that it would be nice to be able to serve from classpath (with a single jar)

Yeah. Malcolm will probably tell us soon that it's done and we just haven't found it. 😛

For serving reaources, an example is at the of this file https://github.com/juxt/yada/blob/master/src/yada/swagger.clj

(new-classpath-resource "/foo)

Sorry, use 'foo' not '/foo'

https://clojurians.slack.com/archives/yada/p1455178416000283 @malcolmsparks: ?

I got a 405

Really? I'll look into that

Ah, did you add a additional path?

You have to add an additional path-info onto the URI, like with dire tory serving

Sorry, hands about to freeze!

Hopefully this bus will arrive soon

So if I 'mounted' my classpath resource at /foo/ I would access a resource prefix+bar with /foo/bar

let me try again

Careful with those slashes!

usually I just try every possibility and pray one works hahaha

Check the Subresources chapter

same 405 error

the new-classpath-resource method looks correct though

I'll take some time to think things through

I'm in the office now, do send me some code and I'll help you figure it out. Are you using bidi btw?

yes I am

In the meantime I'll check that Class/getResource thing - I'm sure it will work, although I only wrote that piece of documentation yesterday and didn't expect anyone to read it yet!

@malcolmsparks: Not a static method, and it returns slightly differently to (io/resource) based on my tests. 😛 We're all watching your commits carefully, maybe you'll have to start branching out.

Hi. I'm getting a validation error when providing handlers in my http responses. :error {:methods {:post {:responses {404 {:response disallowed-key}}}}} (I've been having lots of fun with yada over the past couple of weeks though, of course I only ever say anything unless I think I have a bug... )

Ah, responses is just a resource-level thing right now. So you put it at the resource-level, alongside :methods

Status responses are quite new and I'm sure soon you'll be able to specify them at the method-level, for consistency if nothing else.

@fahey glad you've been having fun with yada, I hope that's both good fun and the usual frustrating 'fun' scrambling up any learning curve

The validation is to protect resource models that yada currently doesn't support - it can be painful getting past the validation step but it's worth having otherwise the code in yada would get horribly complex

Oh, thanks @malcolmsparks ! I would have stared at that for days before figuring it out, if then.

I really like the validation, and it serves as documentation to some extent.

Yada seems fun to me because I can tell that the whole thing is coherent and well-thought out, so it is more like exploring something than just learning a tool.

@fahey good to hear. It's fun for me too, it's been a nice way of learning http

The validation is data, so I think perhaps it's time to publish it in some doc form

@malcolmsparks: That would be useful, especially if there were hints alongside about the coercions/shortcuts.

Yes, it needs its own chapter really, there's lots of shortforms now.

@malcolmsparks: I finally have some time to migrate from 1.0 (0.9-my-own-dev-branch) to 1.1. starting right now

I'll report back on the video upload

the plan is to stream parts through to AWS S3

@stijn Great news - that's one area I want feedback on before release 1.1 final. There is a protocol extension for allowing S3 uploads, but I think we'll need to work together one this

okay, let me first get all the other resources working, it's quite a change

this is application/octetstream right? Not multipart/*

well, that was initially the case, but I think we'll be moving to multipart/* since we are adding a web client too

ok, just checking, both are supported (although I need to check that application/octetstream code - I'll do that tonight)

yes, it's a big change from 1.0->1.1. But I think you'll find it's an improvement once you get used to it

S3 uploads are multipart/* too

yes, the S3 extension would cope with any upload

have an S3 extension built-in would be very cool

the best resource is still examples/phonebook

ok, i'll look into that

I'm still trying to document everything but it's hard work and slow going

😄

The features are pretty much done, but the docs need some work 😞

@stijn just ping me in this slack channel if you need any help or confused by anything

I tend to check-in at least twice a day

ok, will do

HSTS is done: https://twitter.com/malcolmsparks/status/697924162321571840