3 ms·
This is really great news and I’ve been waiting for a while. I use this extensively on gitlab and these little pages sites are easier to use than markdown. Ho
by prepend 6y ago
This is really great news and I’ve been waiting for a while.
I use this extensively on gitlab and these little pages sites are easier to use than markdown.
However one thing that’s cool about GitLab is that we host it internally so any “public” site is available to anyone on the intranet without needing to log in. So the project sites started getting read by lots of users who don’t have GitLab logins and would never commit to a repo.
I wish there was a way to link my orgs logins with GitHub so non-GitHub licensed users could view the sites. I mean, I can do that but I have to then buy GitHub licenses and make them create GitHub accounts just to view project docs. That’s pretty expensive compared to just keeping projects on my internal GitLab.
- codazoda 6y agoThis. When I read the title I was really excited. All of my GitHub users can already access private wikis. It's nice that I can now publish a site to those same users, but I'd like to write docs for the non-technical users at my company without making them public. It would be nice if I could restrict a site to people on my company VPN or, better yet, an IP range.
- osgovernment 6y agoSetup a gateway to do this or host your own GitLab. GitHub Pages uses a shared IP. Blocking based on IP would require them to rework their infrastructure.
- johannes1234321 6y agoVPN and IP won't help - the trend is too move out of VPN. A big threat is always internal and byod opens up the intranet to all risks from the outside. The solution needed is to allow oauth-style authentication of corporate users.