{"id":82015,"date":"2026-09-18T18:03:44","date_gmt":"2026-09-18T12:33:44","guid":{"rendered":"https:\/\/www.tothenew.com\/blog\/?p=82015"},"modified":"2026-10-27T22:56:53","modified_gmt":"2026-10-27T17:26:53","slug":"set-up-an-eds-universal-editor-project-in-adobe-experience-cloud-manager-with-a-private-repository","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/set-up-an-eds-universal-editor-project-in-adobe-experience-cloud-manager-with-a-private-repository\/","title":{"rendered":"Set up an Edge Delivery Services site with Universal Editor using a private repository"},"content":{"rendered":"

Introduction<\/h1>\n

When setting up an EDS project using either Universal Editor or Document Authoring (DA), it is generally recommended that the project repository be public. However, maintaining a public repository is not always feasible, as many clients prefer private repositories due to security, compliance, and organizational requirements.<\/p>\n

Currently, there is no dedicated documentation that provides a comprehensive guide for setting up an EDS project using a private repository.<\/p>\n

This article provides a detailed guide to setting up an EDS Universal Editor project with a private GitHub<\/strong> repository in Adobe Cloud Manager, including the required configuration and setup steps.<\/p>\n

Other Git Providers<\/h2>\n

If you are using a Git provider other than GitHub, such as GitLab<\/strong>, Bitbucket<\/strong>, or Azure DevOps<\/strong>, the setup requires an additional webhook when the repository is routed through Cloud Manager. Refer to this article<\/a> for more info.<\/p>\n

Steps<\/h1>\n

1. Setup a new EDS project using the boilerplate:<\/h2>\n

https:\/\/github.com\/adobe-rnd\/aem-boilerplate-xwalk<\/a><\/p>\n

Open the above link > <\/strong>Click Use this template > <\/strong>Click Create a new repository<\/strong><\/p>\n

Note<\/strong>: You must log in to your GitHub account to see the above option.<\/p>\n

Set the repository to private<\/strong> while creating it.<\/p>\n

2. Update the fstab.yaml file. It should look like this:<\/h2>\n

\"fstab<\/p>\n

url = https:\/\/<aem-author>\/bin\/franklin.delivery\/<github username or org name>\/<repository name>\/main<\/p>\n

Note<\/strong>: You can get the <aem-author> from your cloud manager. Select an author environment where you will be setting up your project and check the URL in the browser.<\/p>\n

3. Install the AEM sidekick extension<\/h2>\n

https:\/\/chromewebstore.google.com\/detail\/aem-sidekick\/igkmdomcgoebiipaifhmpfjhbjccggml<\/a><\/p>\n

4. Use the AEM code sync<\/h2>\n

Visit <\/strong>https:\/\/github.com\/apps\/aem-code-sync<\/a> > <\/strong>Click Configure > Select your repo > <\/strong>Click Save<\/strong>
\n<\/strong>After clicking save, you will be redirected to this screen:<\/p>\n

\"first<\/p>\n

Click Next<\/strong><\/p>\n

\"second<\/p>\n

Add your email for admin<\/strong> and add other emails for different roles as required > Click Next<\/strong><\/p>\n

\"third<\/p>\n

Click Save<\/strong>,\u00a0<\/strong>and you will be redirected to the below screen.<\/p>\n

\"fourth<\/p>\n

Now, refresh the page, and if it becomes like this:<\/p>\n

\"fifth<\/p>\n

You will have to log in to your Sidekick extension.<\/p>\n

For that, click on the profile icon on the page and log in with the same email that you made admin<\/strong> earlier.<\/p>\n

Now, refresh the page, and if you are redirected to the below page, everything is good. You can go to the next step.<\/p>\n

\"first<\/p>\n

 <\/p>\n

5. Configure your repo inside the cloud manager:<\/h2>\n

Go to cloud manager > <\/strong>Click Hamburger icon > Repositories > <\/strong>Click Add repository<\/strong>
\nand do the needful steps<\/p>\n

6. Set up the EDS site inside Cloud Manager:<\/h2>\n

Go to Cloud Manager > <\/strong>Click hamburger icon > Edge Delivery Sites > <\/strong>Click Add Edge Delivery Site<\/strong>
\nWhen the status changes to verified, click on 3 dots > <\/strong>Click Bring your own Git<\/strong><\/p>\n

Follow the below steps to add the secret generated in Cloud Manager using the admin API:<\/p>\n

a) Store the secret in cm-byog using the curl below:<\/strong><\/p>\n

curl -v -X POST https:\/\/admin.hlx.page\/config\/<org>\/sites\/<site>\/secrets\/cm-byog.json <\/em>\r\n \u00a0-H 'content-type: application\/json' <\/em>\r\n \u00a0-H 'x-auth-token: <your-auth-token>' <\/em>\r\n \u00a0--data '{<\/em>\r\n \u00a0\u00a0\u00a0\"value\": \"<secret from cloud manager>\"<\/em>\r\n\u00a0\u00a0}'<\/em><\/pre>\n
Expected Response<\/strong>:<\/p>\n
\"secret<\/p>\n
Note<\/strong>:<\/p>\n
    \n
  1. In the URL, org<\/strong> = your organization name or your GitHub username, and site<\/strong> = your repository name<\/li>\n
  2. You can get the “auth-token<\/strong>” by inspecting it in the browser and then clicking on the “Fetch Users<\/strong>” button on the below page: https:\/\/tools.aem.live\/tools\/user-admin\/index.html<\/a>. Look for the “x-auth-token<\/strong>” in the headers for the access.json network call.<\/li>\n<\/ol>\n
    b) Now that the secret is stored, add it to the site using the curl below:<\/strong><\/p>\n
    curl -v -X POST https:\/\/admin.hlx.page\/config\/<org>\/sites\/<site>\/code.json <\/em>\r\n \u00a0-H 'content-type: application\/json' <\/em>\r\n \u00a0-H 'x-auth-token: <your-auth-token>' <\/em>\r\n \u00a0--data '{<\/em>\r\n \u00a0\u00a0\u00a0\"source\": {<\/em>\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\"url\": \"https:\/\/cm-repo.adobe.io\/api\",<\/em>\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\"raw_url\": \"https:\/\/cm-repo.adobe.io\/api\/raw\",<\/em>\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\"owner\": \"<program-id>\",<\/em>\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\"repo\": \"<repository-id>\",<\/em>\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\"type\": \"byogit\",<\/em>\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\"secretId\": \"cm-byog\"<\/em>\r\n \u00a0\u00a0\u00a0}<\/em>\r\n\u00a0\u00a0}'<\/em><\/pre>\n
    Expected Response<\/strong>:<\/p>\n
    \"secret<\/p>\n
    Note<\/strong>:
    \nYou can get the “program-id<\/strong>” and “repository-id<\/strong>” by inspecting it in the cloud manager and refreshing the repositories page. Search for the \u201crepo\u201d keyword in network calls and look for your repository name in the response of that API call.<\/p>\n
    Now that the secret has been configured using the admin API:<\/p>\n
    Click on 3 dots > select code sync<\/strong><\/p>\n
    7. Now follow the rest of the tutorial to create a site in Cloud Manager and start working with the universal editor:<\/h2>\n
    https:\/\/www.aem.live\/developer\/ue-tutorial#create-an-aem-site<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
    Introduction When setting up an EDS project using either Universal Editor or Document Authoring (DA), it is generally recommended that the project repository be public. However, maintaining a public repository is not always feasible, as many clients prefer private repositories due to security, compliance, and organizational requirements. Currently, there is no dedicated documentation that provides […]<\/p>\n","protected":false},"author":1707,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":3,"footnotes":""},"categories":[5868],"tags":[9091,8888,8891,8890],"class_list":["post-82015","post","type-post","status-publish","format-standard","hentry","category-adobe","tag-edgedeliveryservices","tag-eds","tag-privaterepository","tag-universaleditor"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t