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 ;)
According to their documentation [1] it does work with private repos.
GitLab Pages
51–60 of 317 posts
Re: GitLab Pages
#52Gitlab 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.
Re: GitLab Pages
#53This 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.
Clourfare provides free SSL - just proxy through them.
edit: disregard, I was wrong.
If I'm not mistaken, you have to change the DNS of the domain to something *.cloudflare.com to be able to use their service, so it won't work in this scenario.
Re: GitLab Pages
#54This is awesome. One question I have in comparison to GitHub Pages is if a global CDN is used and if there is effective DDOS protection built in. GitHub has to deal with regular DDOS attacks, and I imagine GitLab will have a few too. GitHub does a pretty good job with it, but before I move to GitLab Pages I'd like to understand that better but didn't see that info anywhere.
Right now, GitLab Pages is hosted on the same servers as GitLab.com, so it gets the same attention from our engineers in terms of reliability and uptime. We're not using a global CDN, but this is something we will explore.
We're working on adding Cloudflare in front of GitLab Pages in https://gitlab.com/gitlab-com/operations/issues/75
We don't have a lot of experience yet with DDOS protection so there might be downtime as we learn that. As you can see in the issue we're working to implement protection before we need it but it might not be ready in time nor can it protect against everything.
Re: GitLab Pages
#55I especially like that they have added configuration options to the .gitlab-ci.yml. If I am not mistaken, this means your project can auto-deploy using an arbitrary build process. Here's what an example .gitlab-ci.yml looks like with a GitLab Pages build configuration: https://gitlab.com/pages/pages.gitlab.io/blob/master/.gitlab... A couple friends and I made something similar for GitHub Pages using Travis CI as our…
Thanks!
You can indeed have a fully automated deployment. You could already do this with GitLab CI on an external server (S3 or anything else), but now you don't have to worry about hosting anymore.
We took inspiration from .travis.yml when designing the .gitlab-ci.yml file, but are continuing to add features and configurations that make it possible to work together with other GitLab features such as build artifacts and now Pages.
Re: GitLab Pages
#56Still looks like GitLab EE only :(
GitLab.com runs GitLab EE, which you can use for free.
Re: GitLab Pages
#57This is awesome. One question I have in comparison to GitHub Pages is if a global CDN is used and if there is effective DDOS protection built in. GitHub has to deal with regular DDOS attacks, and I imagine GitLab will have a few too. GitHub does a pretty good job with it, but before I move to GitLab Pages I'd like to understand that better but didn't see that info anywhere.
Better to ask about their minimum availability guarantee. Knowing that the servers can handle a DDOS attack is of little value if the service goes down for maintenance every day (just to give an example).
GitLab.com runs the same GitLab as our users and some upgrades require downtime. Other operations should not require downtime, we have multiple application servers and load balancers. The backend services are HA except the file storage until we complete the move to CephFS.
Re: GitLab Pages
#58should definitely be prosecuted IMO
Re: GitLab Pages
#59Earlier 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/
Out of curiousity, would you consider GPL Affero sufficiently FOSS?
Re: GitLab Pages
#60Earlier quoted context omitted.
Same. I'm @kel on github and twitter but that's taken on here and gitlab. I emailed to ask since it was just being squatted on but gitlab told me no.
Wow. Well, if that's the case I'll never be using Gitlab then. :( I'd pay money to have my username, too.
Unfortunately, you won't be able to claim a username that is already taken. That would be unfair to other users.
GitLab.com is growing fast, but most people should be able to still claim their username.
Of course, you always have the option to run your own instance relatively easily [0].