Bump Theme 5.18

Author: russfeld

.github/workflows/gh-pages.yml

@@ -22,11 +22,11 @@ jobs:
       - name: Setup Hugo
         uses: peaceiris/actions-hugo@v2
         with:
-          hugo-version: '0.101.0'
+          hugo-version: '0.117.0'
           # extended: true
 
       - name: Build
-        run: hugo --config github.toml
+        run: hugo -b "https://ksu-cs-textbooks.github.io/cis308/"
 
       - name: Deploy
         uses: peaceiris/actions-gh-pages@v3

.gitlab-ci.yml

@@ -1,50 +1,50 @@
-image: docker:20.10.11
+# image: docker:20.10.11
 
-variables:
-  # When using dind service, you must instruct docker to talk with the
-  # daemon started inside of the service. The daemon is available with
-  # a network connection instead of the default /var/run/docker.sock socket.
-  #
-  # The 'docker' hostname is the alias of the service container as described at
-  # https://docs.gitlab.com/ee/ci/docker/using_docker_images.html#accessing-the-services
-  #
-  # If you're using GitLab Runner 12.7 or earlier with the Kubernetes executor and Kubernetes 1.6 or earlier,
-  # the variable must be set to tcp://localhost:2375 because of how the
-  # Kubernetes executor connects services to the job container
-  # DOCKER_HOST: tcp://localhost:2375
-  #
-  DOCKER_HOST: tcp://docker:2375
-  #
-  # This instructs Docker not to start over TLS.
-  DOCKER_TLS_CERTDIR: ""
-  # 
-  # Checkout submodules recursively
-  GIT_SUBMODULE_STRATEGY: recursive
+# variables:
+#   # When using dind service, you must instruct docker to talk with the
+#   # daemon started inside of the service. The daemon is available with
+#   # a network connection instead of the default /var/run/docker.sock socket.
+#   #
+#   # The 'docker' hostname is the alias of the service container as described at
+#   # https://docs.gitlab.com/ee/ci/docker/using_docker_images.html#accessing-the-services
+#   #
+#   # If you're using GitLab Runner 12.7 or earlier with the Kubernetes executor and Kubernetes 1.6 or earlier,
+#   # the variable must be set to tcp://localhost:2375 because of how the
+#   # Kubernetes executor connects services to the job container
+#   # DOCKER_HOST: tcp://localhost:2375
+#   #
+#   DOCKER_HOST: tcp://docker:2375
+#   #
+#   # This instructs Docker not to start over TLS.
+#   DOCKER_TLS_CERTDIR: ""
+#   # 
+#   # Checkout submodules recursively
+#   GIT_SUBMODULE_STRATEGY: recursive
 
-services:
-  - docker:20.10.11-dind
+# services:
+#   - docker:20.10.11-dind
 
-before_script:
-  - docker info
-  - docker login -u $CI_REGISTRY_USER -p $CI_REGISTRY_PASSWORD $CI_REGISTRY
+# before_script:
+#   - docker info
+#   - docker login -u $CI_REGISTRY_USER -p $CI_REGISTRY_PASSWORD $CI_REGISTRY
 
-build-latest:
-  stage: build
-  only:
-    - tags
-  script:
-    - docker pull $CI_REGISTRY_IMAGE:latest || true
-    - docker build --cache-from $CI_REGISTRY_IMAGE:latest --tag $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA --tag $CI_REGISTRY_IMAGE:latest .
-    - docker push $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA
-    - docker push $CI_REGISTRY_IMAGE:latest
-
-# build-branches:
+# build-latest:
 #   stage: build
-#   except:
-#     - master
-#     - main
+#   only:
+#     - tags
 #   script:
-#     - docker pull $CI_REGISTRY_IMAGE:$CI_COMMIT_BRANCH || true
-#     - docker build --cache-from $CI_REGISTRY_IMAGE:latest --tag $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA --tag $CI_REGISTRY_IMAGE:$CI_COMMIT_BRANCH .
+#     - docker pull $CI_REGISTRY_IMAGE:latest || true
+#     - docker build --cache-from $CI_REGISTRY_IMAGE:latest --tag $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA --tag $CI_REGISTRY_IMAGE:latest .
 #     - docker push $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA
-#     - docker push $CI_REGISTRY_IMAGE:$CI_COMMIT_BRANCH
+#     - docker push $CI_REGISTRY_IMAGE:latest
+
+# # build-branches:
+# #   stage: build
+# #   except:
+# #     - master
+# #     - main
+# #   script:
+# #     - docker pull $CI_REGISTRY_IMAGE:$CI_COMMIT_BRANCH || true
+# #     - docker build --cache-from $CI_REGISTRY_IMAGE:latest --tag $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA --tag $CI_REGISTRY_IMAGE:$CI_COMMIT_BRANCH .
+# #     - docker push $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA
+# #     - docker push $CI_REGISTRY_IMAGE:$CI_COMMIT_BRANCH

Dockerfile

@@ -3,15 +3,15 @@ FROM nginx:alpine as build
 RUN apk add --update \
     wget
 
-ARG HUGO_VERSION="0.101.1"
+ARG HUGO_VERSION="0.117.0"
 RUN wget --quiet "https://github.com/gohugoio/hugo/releases/download/v${HUGO_VERSION}/hugo_${HUGO_VERSION}_Linux-64bit.tar.gz" && \
     tar xzf hugo_${HUGO_VERSION}_Linux-64bit.tar.gz && \
     rm -r hugo_${HUGO_VERSION}_Linux-64bit.tar.gz && \
     mv hugo /usr/bin
 
 COPY ./ /site
 WORKDIR /site
-RUN hugo --config docker.toml
+RUN hugo -b "https://cis301.textbooks.cs.ksu.edu/"
 
 #Copy static files to Nginx
 FROM nginx:alpine

config.toml

@@ -20,7 +20,7 @@ theme = "hugo-theme-relearn"
 # TELE - Teleprompter
 # EMBED - Embeddable Version
 [outputs]
-  home = ["HTML", "RSS", "PRINT", "JSON"]
+  home = ["HTML", "RSS", "PRINT", "SEARCH", "SEARCHPAGE"]
   section = ["HTML", "RSS", "PRINT", "TELE", "EMBED"]
   page = ["HTML", "RSS", "PRINT", "TELE", "EMBED"]
 
@@ -87,7 +87,9 @@ theme = "hugo-theme-relearn"
   # this can be overridden in the pages frontmatter
   ordersectionsby = "weight"
   # Change default color scheme with a variant one. Eg. can be "red", "blue", "green" or an array like [ "blue", "green" ].
-  themeVariant = ["light-theme", "dark-theme"]
+  themeVariant = ["auto", "light-theme", "dark-theme"]
+  # The first element is the variant for light mode, the second for dark mode
+  themeVariantAuto = ["light-theme", "dark-theme"]
   # Change the title separator. Default to "::".
   # titleSeparator = "-"
   # If set to true, the menu in the sidebar will be displayed in a collapsible tree view.

content/0-chapter/_index.md

@@ -2,8 +2,8 @@
 title = "Getting Started"
 date = 2018-08-24T10:53:05-05:00
 weight = 1
-chapter = true
+archetype = "chapter"
+ordinal = "0"
 pre = "<b>0. </b>"
 +++
 
-# Getting Started

content/1-chapter/_index.md

@@ -2,10 +2,8 @@
 title = "C Basics"
 date = 2018-08-24T10:53:05-05:00
 weight = 2
-chapter = true
+archetype = "chapter"
+ordinal = "1"
 pre = "<b>1. </b>"
 +++
 
-### Chapter 1
-
-# C Basics

content/2-chapter/_index.md

@@ -2,9 +2,8 @@
 title = "Arrays, Strings, and Files"
 date = 2018-08-24T10:53:05-05:00
 weight = 3
-chapter = true
+archetype = "chapter"
+ordinal = "2"
 pre = "<b>2. </b>"
 +++
-### Chapter 2
 
-# Arrays, Strings, and Files

content/3-chapter/_index.md

@@ -2,10 +2,9 @@
 title = "Pointers and Dynamic Memory"
 date = 2018-08-24T10:53:05-05:00
 weight = 4
-chapter = true
+archetype = "chapter"
+ordinal = "3"
 pre = "<b>3. </b>"
 +++
 
-### Chapter 3
 
-# Pointers and Dynamic Memory

content/4-chapter/_index.md

@@ -2,10 +2,7 @@
 title = "Structs"
 date = 2018-08-24T10:53:05-05:00
 weight = 5
-chapter = true
+archetype = "chapter"
+ordinal = "4"
 pre = "<b>4. </b>"
 +++
-
-### Chapter 4
-
-# Structs

content/5-chapter/_index.md

@@ -2,28 +2,24 @@
 title = "Multiple Files"
 date = 2018-08-24T10:53:05-05:00
 weight = 6
-chapter = true
+archetype = "chapter"
+ordinal = "5"
 pre = "<b>5. </b>"
 +++
 
-### Chapter 5
 
-# Multiple Files
-
-<div align="left">
 Up to this point, all of our programs have been written within a
 single file. There is nothing wrong with this – a C program is just
 a bunch of functions, and it's fine to group those functions within a
 single file. However, as your programs get bigger, it's nice to
 physically separate functions into different files. This makes it
 easier to find certain pieces of your program.
-</div>
-<div align="left">
+
 Separating functions also promotes reuse. Right now, if we
 wanted to reuse a function we’d written in another program, we would
 have to copy it from our old program to our new one. With
 multiple files, we can separate the functions we want reused and
 just link to that file when we want to use them (this is like
 separating the C library functions and including them when we
 want to use them).
-</div>
+