4 ms·

If you're not aware, you get most of that for free with GitHub pages: https://pages.github.com/ https://pages.github.com/ It deploys when you push, is based o

If you're not aware, you get most of that for free with GitHub pages: https://pages.github.com/ https://pages.github.com/ It deploys when you push, is based on Jekyll, and GitHub handles all of the hosting/HTTPS/caching themselves.

davchana 8y ago
Gitlab too does this, along with free unlimited private repos & published static sites; html n Jekyll n all. Just a happy user.
- dsumenkovic 8y ago
  Glad to hear that you enjoy using GitLab! Here's a link if anyone wondered https://about.gitlab.com/product/pages/ https://about.gitlab.com/product/pages/
- kennydude 8y ago
  Gitlab also lets you generate them with whatever you want as it just publishes a result from CI to the pages system
bastawhiz 8y ago
You're forced to use Jekyll, though, and you're forced to use Github. Netlify lets you generate your site however you want and doesn't tie you to a git provider.
- pkd 8y ago
  You're not forced to use Jekyll. You just get some nice things if you do. As long as you have a pages repo with an index.html in the root, GitHub can serve it for you. How you generate the repo is completely up to you. I have my own custom static site generator that I use to publish my blog, I use that with a script that does some git dance to keep things clean and it just works.
  - lloeki 8y ago
    If you don't use Jekyll (let's say, e.g Hugo) you have to commit the content/artefacts to be published to the repo. Committing artefacts to a repo, even if it's a dedicated branch with a separate root, always seemed like a glorious hack to me with consequences such as CI needing push access to the repo. GitLab CI+Pages doesn't need such a hack but then, competing with that would mean GitHub would basically have to allow running arbitrary process during the publish pipeline, which means they'd enter CI space.
paulcarroty 8y ago
Github pages are limited for 50k views per month.

davchana 8y ago

Gitlab too does this, along with free unlimited private repos & published static sites; html n Jekyll n all. Just a happy user.

dsumenkovic 8y ago
Glad to hear that you enjoy using GitLab! Here's a link if anyone wondered https://about.gitlab.com/product/pages/ https://about.gitlab.com/product/pages/
kennydude 8y ago
Gitlab also lets you generate them with whatever you want as it just publishes a result from CI to the pages system

bastawhiz 8y ago

You're forced to use Jekyll, though, and you're forced to use Github. Netlify lets you generate your site however you want and doesn't tie you to a git provider.

pkd 8y ago
You're not forced to use Jekyll. You just get some nice things if you do. As long as you have a pages repo with an index.html in the root, GitHub can serve it for you. How you generate the repo is completely up to you. I have my own custom static site generator that I use to publish my blog, I use that with a script that does some git dance to keep things clean and it just works.
- lloeki 8y ago
  If you don't use Jekyll (let's say, e.g Hugo) you have to commit the content/artefacts to be published to the repo. Committing artefacts to a repo, even if it's a dedicated branch with a separate root, always seemed like a glorious hack to me with consequences such as CI needing push access to the repo. GitLab CI+Pages doesn't need such a hack but then, competing with that would mean GitHub would basically have to allow running arbitrary process during the publish pipeline, which means they'd enter CI space.

paulcarroty 8y ago

Github pages are limited for 50k views per month.