Leveraging repoless approach for crosswalk projects

[josephambrose]

I want to leverage the repo less approach for my new EDS cross walk project, where four developers will be working collaboratively. Each developer will create their own feature branch in GitHub. Before merging their changes into the dev branch, they need to test their individual features separately.

In the repo less documentation, Adobe mentions that it is possible to create multiple sites within a single repository. If we want to create a site for our cross walk project, what should be specified in the Content Source URL?

Additionally, how can we configure the setup to allow each developer to test their features independently on their respective branches?

[ShaileshBassi · Accepted solution]

Hi @josephambrose 

The source url for this would be 

"content": {
        "source": {
            "url": "{{author_host}}/bin/franklin.delivery/{org}/{site}/main",
            "type": "markup",
            "suffix": ".html"
        }
}

Reference - https://www.aem.live/docs/admin.html#tag/siteConfig/operation/createSiteSite

Hope this helps!

Thanks

[josephambrose]

Thanks @ShaileshBassi I'll try this solution. But before that, as per the documentation, we have to create the organization first. I have downloaded the Admin API postman collection and configured it. Authorization part is little confusing here.

I have logged in using https://admin.hlx.page/auth/adobe url and got the auth_token from cookie.. But I am getting 401-unauthorized when i hit the create organization API. Here is the screenshot : 

Am I missing anything? 

[ShaileshBassi]

Hi @josephambrose 

You can hit the url https://admin.hlx.page/auth/adobe and from here it will ask your credentials. Once done it will show you sometime like 

Now navigate to chrome tools -> application. From the cookie you will be able to get the authorization token.

Hope this helps!

Thanks.

[josephambrose]

Hi @ShaileshBassi I did the same and I have copied the auth_token cookie from application tab and pasted it in Authorization part of Postman client. 

It got reflected on Headers part as shown in the below screenshot:

But I am getting 401-unauthorized only.

[josephambrose]

1. We have to get the administrator privilege from Adobe to create the organization

2. We have to mention Authorization as No Auth and In Headers, we have to add x-auth-token while creating the site.

[josephambrose]

Hi @ShaileshBassi 

Consider If we want to create two sites namely, "pocfeature1site" and "pocfeature2site", when we use "Create Site Config" Admin API, shall we mention the URLs as follows:

 first site  : "url": "{{author_host}}/bin/franklin.delivery/{org}/pocfeature1site/main"

 second site : "url": "{{author_host}}/bin/franklin.delivery/{org}/pocfeature2site/main"

(not at the same time, first create one site with name "pocfeature1site" and then create another site  "pocfeature2site." ) Is it correct?