when active, the entire site is locked behind a basic password page. the user has to type in the password to the view the site. this works like logging in and stays active in a session. THIS IS FOR PUBLIC VIEWING. i.e. so that trusted friends and family can view the site without making the entire thing plainly public. sort of like when a tumblr blog is password protected
this of course stops showing up when an admin logs in too. (they can just go directly to /auth/login to bypass it since it is effectively the same thing)
it might be quite big/experimental to implement, maybe use base to catch every page, with exception on /auth/login. i think this should be considered a core feature since ease of sharing in a web page is part of the scope, but a constant public web page may not suit some/most users. i also would like this feature TBH. we will just have to see it doesnt cause too many major issues implementing it at this stage and not earlier on.
when active, the entire site is locked behind a basic password page. the user has to type in the password to the view the site. this works like logging in and stays active in a session. THIS IS FOR PUBLIC VIEWING. i.e. so that trusted friends and family can view the site without making the entire thing plainly public. sort of like when a tumblr blog is password protected
this of course stops showing up when an admin logs in too. (they can just go directly to /auth/login to bypass it since it is effectively the same thing)
it might be quite big/experimental to implement, maybe use base to catch every page, with exception on /auth/login. i think this should be considered a core feature since ease of sharing in a web page is part of the scope, but a constant public web page may not suit some/most users. i also would like this feature TBH. we will just have to see it doesnt cause too many major issues implementing it at this stage and not earlier on.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
when active, the entire site is locked behind a basic password page. the user has to type in the password to the view the site. this works like logging in and stays active in a session. THIS IS FOR PUBLIC VIEWING. i.e. so that trusted friends and family can view the site without making the entire thing plainly public. sort of like when a tumblr blog is password protected
this of course stops showing up when an admin logs in too. (they can just go directly to /auth/login to bypass it since it is effectively the same thing)
it might be quite big/experimental to implement, maybe use base to catch every page, with exception on /auth/login. i think this should be considered a core feature since ease of sharing in a web page is part of the scope, but a constant public web page may not suit some/most users. i also would like this feature TBH. we will just have to see it doesnt cause too many major issues implementing it at this stage and not earlier on.
this can easily be done with nginx