README.md

Childmortality

CI/CD

Deployed on kube-rp both on staging and qa envs.

env	git branch	wordpress admin	cme url
staging	develop	http://wordpress.staging.cme.redpelicans.com/wp-admin/	http://cme.staging.redpelicans.com/
qa	master	http://wordpress.qa.cme.redpelicans.com/wp-admin/	http://cme.qa.redpelicans.com/

WordPress admin:

  Username: root
  Password: p******

Setup

Wordpress

1. install and activate plugins

• Only Rest API by Braad Martin v1.0.0
• ACF to REST API v3.1.0
• Advanced Custom Fields v4.4.12
• Custom Post Type UI v1.6.1
• Tuxedo Big File Uploads v1.0.0
• WordPress importer v0.6.4

2. export/import advanced custom fields

• export Custom Fields > Tools > export (JSON file)
• import Custom Fields > Tools > import

3. export/import custom post types

• export CPT UI > Tools > Copy (JSON)
• import Tools > WordPress run importer > choose file

4. export/import data

• Tools > Export (XML file)
• Tools > Import > WordPress run importer > choose file

check users roles (there are not properly set after import)

Kubernetes

ConfigMap

2 ConfigMaps are used to mount config.json in containers. Because there is yet no way to update them they are not managed in CI/CD pipelines.

First create ConfigMap for all envs:

$ kubectl create configmap cme-config-staging --from-file=config=params/staging.json
$ kubectl create configmap cme-config-qa --from-file=config=params/qa.json

List them:

$ kubectl get configmaps
NAME                 DATA      AGE
cme-config-qa        1         6m
cme-config-staging   1         6m

Delete one:

$ kubectl delete configmaps cme-config-qa

Jira

https://redpelicans.atlassian.net