get-website-package #9
jem
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "get-website-package"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@ -2,3 +2,2 @@mkdir $BUILDDIRmkdir $SOURCEDIR# TODO:TODO ?
forgot to remove it
@ -14,3 +19,1 @@touch $HASHFILEDIR/$hashfilenamecurrentHash=$( cat $HASHFILEDIR/$hashfilename )newHash=$( get-hash-data )touch ${HASHFILEDIR}/${datefilename} $HASHFILEDIR/$hashfilenamepls use ${}
done
@ -20,0 +22,4 @@currentDate=$( cat ${HASHFILEDIR}/${datefilename} )newDate=$( get-date )echo "Local package date: $(date -d "$currentDate"), Remote package date: $(date -d "$newDate")"if [[ $(date -d "$currentDate" +%s) -ge $(date -d "$newDate" +%s) ]] && [[ -n "$currentDate" ]] thenwhat happens if
The script will fail when fetching the package file download url
The latest packed will be downloaded
@ -24,0 +23,4 @@::web/redirects::web/build-website::web/use-basic-auth::web/basic-auth-secret]))secrets may not be contained in config!
This is not the secret itself but the secrets name, i used the naming from c4k-common for consistency but it's confusing, maybe we should change it in c4k-common aswell
addendum: in c4k-common the ingress module checks whether there is a value for the key basic-auth-secret in the config (which, as far as i see, is the name for the secret) and applies basic-auth if there is a value
@ -48,2 +53,3 @@:average-rate 20:burst-rate 40})):burst-rate 40:use-basic-auth false})):use-basic-auth maybe redundant - might be calculated soly by presence or absence of auth elements?
What is the build-website default ?
I tried to do this, but i failed at finding a way to set a config key value based on the presence of auth elements (which is needed for the ingress-module to configure for basic-auth )
@ -64,6 +79,16 @@(str/replace % value-to-partly-match value-to-inplace) %)col))(defn-spec generate-fogejo-api-package-baseurl string?maybe all the build stuff is worth an new namespace ?
i thought we where planning to replace to build stuff by pulling packages and building the website on repo?
@ -0,0 +1,11 @@apiVersion: v1kind: Secretmetadata:name: BASIC_AUTH_NAMEthe name should be calculated and not configured (for safety & comfort).
done
@ -9,3 +9,3 @@GITREPOURL: REPOURLGITCOMMITURL: COMMITURLGITCOMMITURL: COMMITURLwhy we need this ?
It is from the old mode, where the website is build on the web server and is used to check whether the current deployed commit hash is different from the commit hash on the repo server as far as i know