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
{{ message }}
This repository has been archived by the owner on Jun 8, 2022. It is now read-only.
I've just spent a couple days setting up a fancy unified security / login system for my hosted applications.
I'm using Gazee inside of a Docker container and then using an Nginx Docker as a reverse proxy & SSL termination point. As a result, I'd like the option to disable user authentication in Gazee itself. I understand that having Gazee's server running without HTTP authentication introduces a security risk that I, the end user, take responsibility for.
I'd imagine that behind-the-scenes there would need to be a global user account that Gazee is using for bookmarks and such. Basically, I was thinking of this as a "single user mode" with regard to the bookmark storage in the database and whatever other per-user data Gazee generates & stores.
The text was updated successfully, but these errors were encountered:
Hey, thanks for coming through with the feature request. First one in over a year I believe!
I don't want to say I've abandoned Gazee, but it has been a hot minute since I've worked on it. I was gearing up to do a DB overhaul, and then life got in the way.
With that in mind, what you want shouldn't be too hard to implement, I just would need to alter a few things. Primarily the way extraction works for comics since I put them in a per user cache. I've got a few ideas around it. Let me see if I can't rock that out this weekend for you.
I've just spent a couple days setting up a fancy unified security / login system for my hosted applications.
I'm using Gazee inside of a Docker container and then using an Nginx Docker as a reverse proxy & SSL termination point. As a result, I'd like the option to disable user authentication in Gazee itself. I understand that having Gazee's server running without HTTP authentication introduces a security risk that I, the end user, take responsibility for.
I'd imagine that behind-the-scenes there would need to be a global user account that Gazee is using for bookmarks and such. Basically, I was thinking of this as a "single user mode" with regard to the bookmark storage in the database and whatever other per-user data Gazee generates & stores.
The text was updated successfully, but these errors were encountered: