Merge pull request #40 from CodeForPhilly/develop

Release: v1.1.16

Author: themightychris

.github/workflows/k8s-deploy.yml

@@ -146,7 +146,7 @@ jobs:
           --install \
           --namespace "${KUBE_NAMESPACE}" \
           --set site.name="${RELEASE_NAME}" \
-          --set site.title="laddr/${RELEASE_NAME}" \
+          --set site.title="codeforphilly/${RELEASE_NAME}" \
           --set site.image.repository="${DOCKER_REGISTRY}/${DOCKER_REPOSITORY}/${DOCKER_PACKAGE}" \
           --set site.image.tag="${RELEASE_NAME}" \
           --set ingress.enabled=true \

docs/operations/deploy-secret.md

@@ -1,24 +1,3 @@
 # Deploy a secret
 
-## Prerequisites
-
-Install the `kubeseal` client command on your local workstation from the latest stable release: <https://github.com/bitnami-labs/sealed-secrets/releases>
-
-## Configure public certificate
-
-Place the public URL for the target cluster's sealed secret's certificate into the `SEALED_SECRETS_CERT` environment variable:
-
-```bash
-export SEALED_SECRETS_CERT=https://sealed-secrets.live.k8s.phl.io/v1/cert.pem
-```
-
-## Encrypt secrets to cluster repository
-
-Create a Kubernetes `Secret` manifest containing one or more key+value pair, and then use the `kubeseal` client to encrypt it into a `SealedSecret` manifest. The target namespace must be provided and will become part of the encryption such that the secret can only be loaded into that namespace. Commit the sealed secret to the cluster's repository under the path `code-for-philly/helm-chart/templates/secrets/` where it will become part of the deployed helm chart:
-
-```bash
-kubeseal \
-    --namespace code-for-philly \
-    -f mysecret.yaml \
-    -w ~/Repositories/cfp-live-cluster/code-for-philly/helm-chart/templates/secrets/mysecret.yaml
-```
+See <https://codeforphilly.github.io/cfp-live-cluster/development/features/sealed-secrets/>

php-config/Emergence/CMS/BlogRequestHandler.config.d/access.php

@@ -0,0 +1,3 @@
+<?php
+
+Emergence\CMS\BlogRequestHandler::$accountLevelWrite = 'Staff';