-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ENDOC-516 7.1 Create Tutorials for WCMS PBC powered by Strapi #607
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First reactions on this although I skimmed the widget section. I want to try out the PVC business myself still and see if we can do anything there...
|
||
Strapi registration is available following bundle installation. To log in to Strapi: | ||
|
||
1. Open a browser tab and enter your App Builder base URL followed by `/entando-strapi/admin/`, e.g. `http://hubdev.okd-entando.org/entando-strapi/admin/` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's not use a development server as an example here. I think you can just change this to https://YOUR-SERVER-URL/entando-strapi/admin/
|
||
#### Entando Strapi Config Application | ||
|
||
All REST APIs are public. No Keycloak role is required. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would remove lines 48-50. I don't think it means anything to the end user.
|
||
#### Entando Strapi Content Template Application | ||
|
||
All REST APIs are private and require the admin role. To add Keycloak role mapping for the `entando-strapi-config` and `entando-strapi-templates` clients: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might remove the first sentence. It seems like an internal detail and it could easily change as the impl evolves.
2. Using the ent CLI, apply the Custom Resource Definitions for the Strapi bundles: | ||
|
||
``` | ||
ent ecr deploy --repo=https://github.com/Entando-Hub/entando-strapi-bundle.git |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does the order matter?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i don't know; order was not advised. i ran the commands in the order they were listed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like they aren't dependent, unlike some of our other PBCs. We can leave it like this for now.
|
||
Entando's Strapi implementation is available from the Entando Cloud Hub via 3 bundles, which must be installed in the Local Hub of the App Builder. | ||
|
||
1. Within your Entando instance, create a persistent volume claim with the following properties: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Create a file named strapi-pvc.yaml with this content:
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: pn-fe9131bb-ca5e5232-entando-strapi-server-pvc
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 2Gi
storageClassName: csi-cinder-high-speed
- Create the PVC using this command:
kubectl apply -f strapi-pvc.yaml -n entando
No description provided.