{"componentChunkName":"component---src-templates-page-js","path":"/gitlab-pages","result":{"data":{"markdownRemark":{"frontmatter":{"title":"To GitLab Pages from AWS CloudFormation and Travis CI","date":"03 September 2018","path":"/gitlab-pages","author":null,"excerpt":"Last year, I had some fun building a Github Page alternative with AWS CloudFormation and Travis CI. In retrospect, there was some clear indication of over-engineering...","tags":["gitlab","web","jekyll","aws","travis-ci","cloudflare","v3"],"coverImage":null},"id":"fdafbfa0-14c4-5287-b321-a224a442c4e1","html":"

Last year, I had some fun building a Github Page alternative with AWS CloudFormation and Travis CI. In retrospect, there was some clear indication of over-engineering.

\n

And with the expiry of my Github Education subscription, a new home is needed for my private repositories. With built-in free CI/CD and unlimited private repos, Gitlab is a godsend. And not forgetting Gitlab Pages for hosting static sites!

\n

Entering the GitLab-land

\n

At the core of the configuration is the .gitlab-ci.yml file.

\n
# requiring the environment of Ruby 2.3.x\nimage: ruby:2.3\n\n# add bundle cache to 'vendor' for speeding up builds\ncache:\n  paths: \n    - vendor/\n\nbefore_script:\n  - bundle install --path vendor\n\n# the 'pages' job will deploy and build your site to the 'public' path\npages:\n  stage: deploy\n  script:\n    - bundle exec jekyll build -d public/\n  artifacts:\n    paths:\n      - public\n  only:\n    - master # this job will affect only the 'master' branch\n\n# To solve encoding error:\nvariables:\n  LC_ALL: \"C.UTF-8\"\n  LANG: \"en_US.UTF-8\"\n  LANGUAGE: \"en_US.UTF-8\"
\n

And the CI build log is such a delight to watch :)

\n

\n \n \n \n \n \n \n

GitLab's build log

\n

\n

Some errors and solutions

\n

Gitlab CI: Conversion error: Jekyll::Converters::Scss encountered an error while converting 'assets/css/style.scss': Invalid US-ASCII character "\\xE2" on line 5

\n

Solution:\nChange encoding to UTF-8.

\n

Reference

\n

Gitlab CI: Filed to extract & 404 HTTP error at the domain name

\n

Solution:\nThe folder must be named public instead of _site etc.

\n

Reference

\n

Browser: Multiple 404 errors returned by .css files

\n

Solution:\nusername.gitlab.io/css/monokai.css is invalid due to the missing repo name in the path.

\n\n

Reference

\n

/Chris

","excerpt":"Last year, I had some fun building a Github Page alternative with AWS CloudFormation and Travis CI. In retrospect, there was some clear…"}},"pageContext":{"type":"posts","next":{"frontmatter":{"path":"/cornell-tech","title":"Release Notes: My Graduation from Cornell Tech CS v3","tags":["cornell-tech","cornell","master","mba","cs","nyc"]},"fileAbsolutePath":"/opt/build/repo/src/posts/2017-06-15-graduation_from_cornell_tech_cs_v3.md"},"previous":{"frontmatter":{"path":"/nyancat-spectrum","title":"Deploy Nyancat Server to Google Cloud using containers in 5 mins","tags":["docker","container","telnet","google-cloud"]},"fileAbsolutePath":"/opt/build/repo/src/posts/2018-10-02-nyancat-server-gcp-container.md"}}},"staticQueryHashes":["1425477374","3128451518"]}