Currently, the paperlesspaper API (and the app) requires network access to your self-hosted integration URL for fetching and rendering.
I'd like to avoid exposing the integrations url to the public. My current example is a configuration of immich, where the immich instance is only available within my internal network. However to display images on paperlesspaper, I deployed this repository next to the immich instance, available from the internet. Doing so with the credentials in .env (like in the sample of this repo) would expose my image library publicly on the internet.
It would be great if the paperlesspaper app and API could provide some authentication for customer integration servers (i.e. sending a configurable API key as header). Currently I've whitelisted the IP address of the paperlesspaper API (and my internal network), but this breaks the app outside my internal network and also depends on the assumption that paperlesspaper does fetch always from the same public API.
Currently, the paperlesspaper API (and the app) requires network access to your self-hosted integration URL for fetching and rendering.
I'd like to avoid exposing the integrations url to the public. My current example is a configuration of immich, where the immich instance is only available within my internal network. However to display images on paperlesspaper, I deployed this repository next to the immich instance, available from the internet. Doing so with the credentials in .env (like in the sample of this repo) would expose my image library publicly on the internet.
It would be great if the paperlesspaper app and API could provide some authentication for customer integration servers (i.e. sending a configurable API key as header). Currently I've whitelisted the IP address of the paperlesspaper API (and my internal network), but this breaks the app outside my internal network and also depends on the assumption that paperlesspaper does fetch always from the same public API.