You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all thanks for providing noembed. I am currently looking through the code and all the image providers seems to use the /i/ prefix for referring to the images.
Would it be possible to add/include the coder for accessing the images as well? It doesn't seem to be just a proxy request
The text was updated successfully, but these errors were encountered:
Right now I am using https://github.com/leedo/web-imageproxy for handling image requests to /i/. It can do image proxying and resizing. It could probably included as a submodule in noembed, and included in the example app.
Hi @leedo,
This is still pending.
I creaded a Docker image for noembed, and would like to complete it's deployment having this.
Could you provide a guide on how you deployed it?
First of all thanks for providing noembed. I am currently looking through the code and all the image providers seems to use the /i/ prefix for referring to the images.
Would it be possible to add/include the coder for accessing the images as well? It doesn't seem to be just a proxy request
The text was updated successfully, but these errors were encountered: