Two questions: 1. Does this work with private repos? 2. Are there traffic limits? (use case e.g. when I reach a HN Top 10 ;)
1. Yes, you can use Pages with private projects
2. No, there are no traffic limits.
GitLab Pages
61–70 of 317 posts
Re: GitLab Pages
#62Earlier quoted context omitted.
I'd say that it's a pretty easy choice. Pick the open source one.
Only Gitlab CE is OSS, GitLab EE is "publicly viewable" but neither FOSS/OSS [1]. It's really a shame because I would pay good money to have GitLab EE under a FOSS license. [1] https://about.gitlab.com/license-faq/
We initially had GitLab EE under the MIT expat license. But this proved to be a problem for potential customers, their purchasing department didn't understand. We also like that now we can store the EE source in a public repository that accepts merge requests.
Re: GitLab Pages
#63Gitlab is still super slow even compared to young projects like gogs. I know many ppl who shied away for gitlab due to its slowness. If I was them, I would stop all copycat 'me too' features like ci/pages ect and put the resources to making it faster. This is a sign that their features are pritorized by business ppl who want to put features on their slides .
gogs was designed from the start to be fast. Nothing but a rewrite would make GitLab as fast as gogs for basic stuff on small self-hosted servers. For basic uses, the resources required for the platform of GitLab (rails) is greater than the resources required to use all of gogs.
Gogs will always use less memory and cpu. We are working to make GitLab page loads very fast.
Re: GitLab Pages
#64Earlier quoted context omitted.
Racist attitudes? Interesting - not sure what you're talking about. Could you link a source?
Their new 'social impact team' isn't a fan of white people https://twitter.com/_danilo/status/690601512813367297 http://www.breitbart.com/tech/2016/02/08/report-anti-white-a...
Holy shit. That's some of the most egregiously racist things I've seen and I'm not white! No business from me, ever!
Elaboration : I feel like apologising for the knee jerk reaction. A tweet I would forgive, but that corporate slide in a corporation that aggressively claims to be social, inclusive, community etc. is simply terrible hypocrisy.
But anyway I checked with my PM and my team uses self hosted gitlab and the decision was purely technical :)
Re: GitLab Pages
#65should definitely be prosecuted IMO
Can you change your username please. HN isn't Reddit.
Re: GitLab Pages
#66This is great -- it has a killer feature that I think GitHub Pages is sorely missing (unless it exists and I'm just ignorant to the fact). Custom domains WITH SSL. Right now I have my custom domain set up on GitHub, but it's not SSL. I would love to be able to do that.
Just for reference—you can achieve this if you run your site behind CloudFlare. I run my own blog this way.
That's not truly end-to-end encrypted though, right? The server -> CloudFlare goes over HTTP.
Re: GitLab Pages
#67Great start. The obvious missing feature is Let's Encrypt support. I would like to see hosting companies like GitLab implement HTTPS for 100% of their served pages, and Let's Encrypt is a key enabling technology to do so.
For this sort of thing, I've had great success sticking arbitrary services behind an nginx reverse proxy on the same network and terminating the SSL at the proxy.
Re: GitLab Pages
#68Congrats on new major feature. One thing I'd like to see developed further is support for per-branch pages. Right now it looks like you could jerryrig a build script that builds each branch in its own subdirectory, but that sounds bit suboptimal considering that any commit will trigger full rebuild of all branches.
Can you elaborate a bit more? Because you are able to restrict builds to certain branches.
Why not have multiple projects in your case?
Re: GitLab Pages
#69Earlier quoted context omitted.
Do you have to hand over your private keys for that?
How would you do that without handing over your private keys? Otherwise gitlab couldn't serve your site. Also, as soon as you point an A record of your domain to somebodies server, they're able to get valid certificates through acme (which is probably what they do). If you don't trust somebody, don't point your domain to them.
> How would you do that without handing over your private keys?
CloudFlare has that figured out https://www.cloudflare.com/keyless-ssl/
Re: GitLab Pages
#70Just want to shout out that you can actually get HTTPS on your custom domained Github Page now with Kloudsec[1]. We actually built a dedicated onboarding tool for this: https://kloudsec.com/github-pages
[1] Kloudsec is a CDN for programmers