When you overtake this deploy and rebrand repo to your network you have to recognize the following changes and doings:
- You have to set
SHOW_CONTENT_FILTER_HEADER_MENU
andSHOW_CONTENT_FILTER_MASONRY_GRID
inbranding/constants/filter.js
originally in main code filewebapp/constants/filter.js
to your preferred value.
- Create your own Mapbox account at https://mapbox.com/ for your organization to get your own Mapbox token.
- You have to add the
MAPBOX_TOKEN
from thedeployment/kubernetes/values.template.yaml
to yourdeployment/kubernetes/values.yaml
and set it to your own Mapbox token.
- You have to add property
target
to all array elements with valueurl
to your preferred value inbranding/constants/headerMenu.js
originally in main code filewebapp/constants/headerMenu.js
. - You have to move value of all
externalLink
to new propertyexternalLink.url
and set new propertyexternalLink.target
to your preferred value inbranding/constants/links.js
originally in main code filewebapp/constants/links.js
.
- You have to set
PROGRESS_BAR_COLOR_TYPE
inbranding/constants/donation.js
originally in main code filewebapp/constants/donation.js
to your preferred value.
- You have to move value of
LOGO_HEADER_CLICK.externalLink
to new propertyLOGO_HEADER_CLICK.externalLink.url
and set new propertyLOGO_HEADER_CLICK.externalLink.target
to your preferred value inbranding/constants/logos.js
originally in main code filewebapp/constants/logos.js
.
- You have to set
LOGO_HEADER_CLICK
inbranding/constants/logos.js
originally in main code filewebapp/constants/logos.js
to your preferred value.
- You have to set
SHOW_GROUP_BUTTON_IN_HEADER
inbranding/constants/groups.js
originally in main code filewebapp/constants/groups.js
to your preferred value.
- You have to add the
CATEGORIES_ACTIVE
from thedeployment/kubernetes/values.template.yaml
to yourdeployment/kubernetes/values.yaml
and set it to your preferred value. - Make sure the correct categories are in your Neo4j database on the server.
Deployment/Rebranding PR – chore: 🍰 Implement PRODUCTION_DB_CLEAN_ALLOW for Staging Production Environments #56
- Copy
PRODUCTION_DB_CLEAN_ALLOW
fromdeployment/kubernetes/values.template.yaml
tovalues.yaml
and set it tofalse
for production environments and only for several stage test servers totrue
.
Upgrade the cert-manager, but install CRDs of the version 1.0.0-alpha to actually be able to upgrade ocelot. Then uninstall the legacy CRDs and install the correct ones.
# upgrade cert-manager to 1.9.1
> helm upgrade --set installCRDs=true --version 1.9.1 --namespace cert-manager cert-manager jetstack/cert-manager
# apply legacy CRDs
> kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.0.0-alpha.1/cert-manager.crds.yaml
# upgrade ocelot
> helm upgrade ocelot ./
# delete legacy CRDs
> kubectl delete -f https://github.com/cert-manager/cert-manager/releases/download/v1.0.0-alpha.1/cert-manager.crds.yaml
# apply CRDs for cert-manager 1.9.1
> kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.9.1/cert-manager.crds.yaml
Background: We had to upgrade cert-manager due to an external dependency - therefore we had to update cert-manager apiVersion cert-manager.io/v1alpha2
to cert-manager.io/v1
.
The error occurring when not doing this is the following:
Error: UPGRADE FAILED: unable to build kubernetes objects from current release manifest: [resource mapping not found for name: "letsencrypt-production" namespace: "" from "": no matches for kind "ClusterIssuer" in version "cert-manager.io/v1alpha2"
ensure CRDs are installed first, resource mapping not found for name: "letsencrypt-staging" namespace: "" from "": no matches for kind "ClusterIssuer" in version "cert-manager.io/v1alpha2"
ensure CRDs are installed first]
- You have to add the
COOKIE_EXPIRE_TIME
from thedeployment/kubernetes/values.template.yaml
to yourdeployment/kubernetes/values.yaml
and set it to your preferred value. - Correct
locale
cookie exploration time in data privacy.
- No information.