ENDOC-443 Auto install Hub sections #446
Conversation
| Install the Customer Portal in two steps by integrating the Entando Hub into your App Builder. | ||
| 1. From the left sidebar of your App Builder, go to the `Repository`. Select `Entando Hub` at the top right side of the page if it has already been configured. If not, enter `Entando Hub` and the API URL to initialize the Hub. It will now be available from this page at any time. | ||
| 1. Log into your `App Builder` → `Repository` → `Select Registry` kebob buttons |
There was a problem hiding this comment.
kebob buttons? Have we used that term before?
There was a problem hiding this comment.
i just think like chicken kebobs :D
There was a problem hiding this comment.
no we haven't elsewhere. I looked it up and it seemed like that's the most common term for the vertical ones. Should I use something else?
There was a problem hiding this comment.
i have never heard of this and was totally confused by it
|
|
||
| 2. From the Hub, deploy and `Install` the two Customer Portal bundles from the Catalog. | ||
| 2. From the Hub Catalog, `Deploy` and `Install` the two Customer Portal bundles. |
There was a problem hiding this comment.
Probably still need to hint at the order - application first then content bundle. The order does matter.
| - The ent command line tool, installed and connected to your Kubernetes instance. | ||
|
|
||
| ### Installation Steps | ||
|
|
||
| ### Auto Install via the Entando Hub |
There was a problem hiding this comment.
In other places we called it Automatic Install (e.g. https://developer.entando.com/v6.3.2/docs/getting-started/#learn-about-entando) I'm not sure shortening it to Auto is clearer.
There was a problem hiding this comment.
changed it to automatic. I was waffling about it too.
|
|
||
| 2. From the Hub Catalog, `Deploy` and `Install` the PDA bundle. It will take a few minutes to install. | ||
|
|
||
| 3. Skip to Step 5 below to continue. |
There was a problem hiding this comment.
Link to the next section by name? The numbers can easily change in markdown so I've "usually" tried to avoid mentioning numbered steps.
| ### Installation Steps | ||
| ### Automatically Access the Hub from the App Builder | ||
| 1. Login to your App Builder | ||
| 2. Got to `Registry` → `Select Registry` kebob buttons |
| 2. In the pop-up window, enter `Entando Hub` and URL [https://hub.entando.com], then `Save` | ||
| 3. Click on the Hub in the Registry | ||
|
|
||
| 2. From the Hub Catalog, `Deploy` and `Install` the four Standard Banking Demo bundles in this order: |
| 3. `standard-demo-manage-users-bundle` | ||
| 4. `standard-demo-content-bundle` | ||
|
|
||
| 3. To navigate to Standard Demo: |
| 1. Login to your App Builder | ||
| 2. Got to `Registry` → `Select Registry` kebob buttons | ||
| 3. Choose `New Registry` | ||
| 4. In the pop-up window, enter `Entando Hub` and URL [https://hub.entando.com], then `Save` |
There was a problem hiding this comment.
"for the URL" like above sounds a little better... comment applies to all other instances below
|
|
||
| ### Automatic Install via the Entando Hub | ||
| Install the Standard Banking Demo by integrating the Entando Hub into your App Builder. | ||
| 1. Log into your `App Builder` → `Repository` → `Select Registry` (kebob menu) |
There was a problem hiding this comment.
I think it's usually kebab rather than kebob. I don't feel strongly about it but since App Builder and Repository are not from the kebab menu it confuses me a little.
|
|
||
| 2. From the Hub Catalog, `Deploy` and `Install` the PDA bundle. It will take a few minutes to install. | ||
|
|
||
| 3. Jump to [Set up permissions](#permissions) below to complete the tutorial. |
There was a problem hiding this comment.
Does this work for you locally? It's failing the link check.
There was a problem hiding this comment.
yes, it does work
plus v6.3.2 landing page uncommenting. After review will apply to v6.3.2.