You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to move arcticdata.io to k8s, we need a way of hosting the existing wordpress instance that serves the root of the https://arcticdata.io/ site.
This should be relatively straightforward by use of a bitnami chart.
Tasks:
Find suitable chart and test-deploy on dev cluster
global.defaultStorageClass: csi-cephfs-sc-ephemeral# (for testing; csi-cephfs-sc for prod)wordpressUsername:
existingSecret: # (create a secret to contain wordpressPassword)
Determine how to export all settings and content from existing ADC wordpress instance, and import into k8s version
mariadb.enabled=falseexternalDatabase.host=myexternalhostexternalDatabase.user=myuserexternalDatabase.password=mypasswordexternalDatabase.database=mydatabaseexternalDatabase.port=3306# If the database already contains data from a previous WordPress # installation, set:wordpressSkipInstall: true
customize ingress to serve wordpress in addition to adc site
The text was updated successfully, but these errors were encountered:
In order to move arcticdata.io to k8s, we need a way of hosting the existing wordpress instance that serves the root of the https://arcticdata.io/ site.
This should be relatively straightforward by use of a bitnami chart.
Tasks:
helm install wpbrooke bitnami/wordpress --version 24.0.7
The text was updated successfully, but these errors were encountered: