You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Go to file
bom 03ac969aa9 bump version to: 1.1.9-SNAPSHOT 6 months ago
doc Update reqs 8 months ago
infrastructure/build bump version to: 1.1.9-SNAPSHOT 6 months ago
public Project skeleton 2 years ago
src Fix format of text field 1 year ago
.gitignore [Skip-CI] Ignore eastwood file 8 months ago
.gitlab-ci.yml Bump versions 6 months ago
LICENSE Project skeleton 2 years ago
README.md [Skip-CI] Add Development and mirrors section 12 months ago
build.py Updated build.py and dependencies 9 months ago
package.json bump version to: 1.1.9-SNAPSHOT 6 months ago
project.clj bump version to: 1.1.9-SNAPSHOT 6 months ago
shadow-cljs.edn Improvements docker image building 7 months ago

README.md

convention 4 kubernetes: c4k-website

Clojars Project pipeline status

DeltaChat chat over e-mail | team@social.meissa-gmbh.de team@social.meissa-gmbh.de | Website & Blog

Purpose

Delivering cryogen generated static sites with the push of a few buttons.

c4k-website generates configuration files for multiple nginx webservers, and corresponding cryogen static site generator build containers. This automatically downloads a <branch>.zip from a specified gitea API url. You need an authorization token to access the specified gitea user account. The build container is based on clojure:lein.

Following the example in valid-config.edn and valid-auth.edn you can add as many websites as you like (provided you have the DNS Routes set up). One set of configmaps, deployment, services etc will be created for each element in the :websites and :auth list.

Configs generated by c4k-website consists of the following parts:

  • nginx deployment + configmap + service + ingress + certificate definitions
  • nginx deployment has init container, building the website at startup time
  • cron job for building and build secret for storing auth data
  • respective volume claims

Status

Stable - we use this setup on production.

Try out

Click on the image to try out in your browser:

Try it out

Your input will stay in your browser. No server interaction is required.

You will also be able to try out on cli:

target/graalvm/c4k-website src/test/resources/website-test/valid-config.yaml src/test/resources/website-test/valid-auth.yaml | kubeval -
target/graalvm/c4k-website src/test/resources/website-test/valid-config.yaml src/test/resources/website-test/valid-auth.yaml | kubectl apply -f -

Usage

You need:

  • DNS routes matching the fqdns in the lists
  • cryogen as a static site generator
  • a cryogen project ready to build
  • a gitea account which holds the buildable project
  • an authorization token for that account
  • and a kubernetes cluster provisioned by provs

Add a unique identifier for each website to config.edn and auth.edn (e.g. domain-name).
Add the list of fqdns, your gitea host, name of the website repo and the respective branch name (usually "main") to config.edn.
Add auth token and gitea user with access to the website repo to auth.edn.
Let c4k-website generate your .yaml file.
Apply this file on your cluster with kubectl apply -f yourApp.yaml.
Done.

Script Execution

Optionally you can specify a trusted script in your config.edn.

  1. sha256sum "/path/to/your/script/file"
  2. copy the output of this command
  3. add the :sha256-output "hash-of-file file.name" :key value pair to the respective collection in :websites.

Also, see the example in valid-config.edn. The script file needs to exist in the <branch>.zip and path specification to the script file should be relative to the root of the unzipped folder. Scripts can be of any type - as long as an according shebang exists in the first line.

sha256sum your-script-file #  use output of this call
sha256sum scripts/your-script-file #  or this
sha256sum scripts/foo/bar/your-script-file #  or this

resource requests and limits

You may want to adjust the resource requests and limits of the build and init containers to your specific scenario.

Development & mirrors

Development happens at: https://repo.prod.meissa.de/meissa/c4k-website

Mirrors are:

For more details about our repository model see: https://repo.prod.meissa.de/meissa/federate-your-repos

License

Copyright © 2022 meissa GmbH Licensed under the Apache License, Version 2.0 (the "License") Pls. find licenses of our subcomponents here