-
-
Notifications
You must be signed in to change notification settings - Fork 4
Description
Is this a new feature request?
- I have searched the existing issues
Wanted change
It would be nice to be able to password protect the configuration interface. The apprise docs say something about configuration of the embedded NGINX in an apprise install to accomplish this but they look to be referring to a non-containerized install. Or I'm wrong about that and there is an NGINX as part of the container image?
If the former, would it be bad practice by Linuxserver.io conventions to front-end the apprise-api with an NGINX container to provide this functionalty?
If the latter, add an extra_args parameter and modify the entrypoint script to consume said variables and set up http auth?
Reason for change
It seems a bit dangerous to leave the service configuration interface unprotected even on a fairly trusted network.
Proposed code change
The changes would be, per the above, to the entrypoint script for the apprise-api container and to the Docker Compose manifest. I don't think any app-level changes would be necessary.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status