@ales.najmann https://shadow-cljs.github.io/docs/UsersGuide.html#_release_specific_vs_development_configuration

:asset-path "/js" :release {:asset-path "/coolapp/js"}

or :dev {:asset-path ...} whichever you prefer

I have trouble understanding how the :proxy-url works. If I make request to localhost:8888/todos/1 I get HTTP 503

seems correct. I'll check

hmm yeah it doesn't like the https for some reason

There was a different proxy method? Would that work with https? I'd like to develop against a existing API that uses https

there is no other built-in proxy method no but I can fix this issue

oh, great!

its just a config error in the code

@pekka I fixed it locally but now I get a 403 Forbidden from cloudflare

it works when I try to access it directly but not through the proxy

and now it appears to have banned me completely since even the ssl handshake fails

ok 😊

other ssl sites I can proxy fine but cloudfare seems to filter the proxy requests

ok, I don't need cloudflare as such, that was just as an example

ah ok

Is your fix something you can release though? That would help me very much!

@pekka fixed in version 2.6.20

great! 🙇

now the request works but since the target uses vhost it gets confused 😄

It would work if the proxy rewrites the Origin

Do you know if undertow(?) supports that?

hmm no idea

you can just use any other http server if that is easier

ok, no problem I can live with this 😄

its just files as far as shadow-cljs is concerned

hmm there is a rewriteHostHeader option for the proxy handler

maybe thats enough?

I woud think so

with TLS SNI it is the only thing the webserver sees before terminating TLS

wonder why it defaults to false

guess I'll add an option for that

@thheller yes, I use :asset-path but alone it does not work, assets have to be produced on specified path with specified :output-dir at least and I don't like that location is different for :dev and :release builds 😞

you can override all options

:release {:output-dir "foo/bar"}

sure, it is just that there are more moving parts in the build. like asset 'copying' and so on and on release build process can be different and one has to do additional checking so that build is correct.

not sure I understand what you mean or what the problem is?

it's more or less nitpicking from my side

reproducibility

if there are different pipelines for dev and release, more moving parts, more stuff can break

well dev is always going to have differences compared to release

but I have been running without :release specific config for years

me too, but this project that I have is different unfortunately 🙂

it actually works, so no worries

@pekka just pushed 2.6.21 which fixed a couple issues with the proxy support and also now supports rewriting the host header

enabled by default :proxy-rewrite-host-header false to disable

:thumbsup:

Seems "change origin" would be the feature that is required. for example

what does that do?

change the Origin-header in the request

doesn't seem to be an option on the undertow Proxy...

I can link through the @cedx/reverse-proxy, so no problem for me, just for further study 😊

What are the https settings in :devtools?

or is https supported on devtools http server?

@pekka https://shadow-cljs.github.io/docs/UsersGuide.html#_ssl enables it for all servers

basic "hello world" example for shadow + hoplon + electron (w/reload): https://github.com/vigilancetech-com/shadow-hoplon-electron

https://github.com/vigilancetech-com/shadow-hoplon-electron/blob/master/package.json#L34

what kind of ancient verison is that? 😛

@clashthebunny I just checked CLJS master and there were 2 changes to the analyzer/compiler that aren't currently compatible. will need to wait for a final release. can't fix them now since that would break the current 1.10.339 release

Great to know. Thanks for being so on top of everything!

seems to work fine with the fixes though. I can push the branch if you are eager to play with master but I think they are getting ready to release "soon" now