First of all, I love the app, and I use it on a daily basis.
Currently I have to enable my VPN in order to access my self-hosted TimeTagger instance.
I deploy it behind a reverse proxy that supports header-based authentication.
If Tagius would support custom headers, I could skip the VPN.
From what I've seen in the code, I think an addition to the existing AuthInterceptor could be the easiest solution, as it already adds a header.
A second interceptor for the custom headers might be a clearer separation of concerns.
If you are fine with external contributors, I would give it a shot. But I totally understand if you are not comfortable with the idea.
In any case, thank you very much for this app. You freed me from a less than ideal web app solution.
First of all, I love the app, and I use it on a daily basis.
Currently I have to enable my VPN in order to access my self-hosted TimeTagger instance.
I deploy it behind a reverse proxy that supports header-based authentication.
If Tagius would support custom headers, I could skip the VPN.
From what I've seen in the code, I think an addition to the existing
AuthInterceptorcould be the easiest solution, as it already adds a header.A second interceptor for the custom headers might be a clearer separation of concerns.
If you are fine with external contributors, I would give it a shot. But I totally understand if you are not comfortable with the idea.
In any case, thank you very much for this app. You freed me from a less than ideal web app solution.