Unable to commit Symlink files for dispatcher from windows | Community
Skip to main content
G
georhe6
Level 4
February 24, 2025
Solved

Unable to commit Symlink files for dispatcher from windows

  • February 24, 2025
  • 4 replies
  • 1022 views

Hi Team,

I am unable to commit symlink created for enabled_Vhost and enabled_Farms from windows machine.
I tried using WSL also but the symlink files are not listing at all. How to resolve this issue.

AEM as CS, Dispatcher , symlink

Best answer by arunpatidar

Hi @georhe6 
Please check if this helps
https://github.com/git-for-windows/git/wiki/Symbolic-Links#creating-symbolic-links 

4 replies

arunpatidar
Community Advisor
arunpatidarCommunity AdvisorAccepted solution
Community Advisor
February 24, 2025

Hi @georhe6 
Please check if this helps
https://github.com/git-for-windows/git/wiki/Symbolic-Links#creating-symbolic-links 

Arun Patidar
    MeasurableBusinessResults
    MeasurableBusinessResults
    Level 3
    October 7, 2025

    Given that this is so cumbersome (I have the same issue in a Windows box without admin priviledges right now),
    and that symbolic links are not really cross-platform compatible (as described in the link you shared: https://gitforwindows.org/symbolic-links.html )
    and that this whole approach of soft-linking available configs to an enabled configs folder is a historic Apache legacy, and MAY make sense on a manually managed server, but in a modern CI/CD devops setup does not make any sense at all imho - because I will not have disabled unused configs lying around on my servers, I will only have active ones, so always available == enabled,

    Why not get rid of the "available" folder completely, and just put the actual files in "enabled"?
    No need for redundant symlinks anymore...

    So the main question is: while Adobe AEM product dev team may need some time to come to the same conclusion, in the meantime can I just put files into "enabled" folder directly if I want to, or will the webtier pipeline complain and fail with an error?

    arunpatidar
    Community Advisor
    arunpatidarCommunity Advisor
    Community Advisor
    October 7, 2025

    Hi @measurablebusinessresults 

    Please check below for folder structure and how to create symlinks in Windows

    https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/content-delivery/validation-debug#flexible-mode-file-structure

     

    Unfortunately you can't put files into "enabled" folder directly.

    Arun Patidar
    Tethich
    Community Advisor
    TethichCommunity Advisor
    Community Advisor
    February 24, 2025

    Hi @georhe6 

     

    I believe you can recreate them or instruct git to allow them (symlinks = true)

    😞https://experienceleague.adobe.com/en/docs/experience-manager-learn/ams/dispatcher/git-symlinks
    https://gist.github.com/huenisys/1efb64e57c37cfab7054c65702588fce

    Try to see if any of these two links leads you to a fix.

      giuseppebaglio
      giuseppebaglio
      Level 10
      February 24, 2025

      To address the issue at hand, it is important to follow a systematic approach. Here are the steps to consider for resolving the matter:

       

      1. Enable symlink support in Git

       

      git config --global core.symlinks true​

       

      • Create symlinks with elevated privileges using mklink from Command Prompt or PowerShell as an Administrator:

       

      mklink enabled_Vhost path\to\target\Vhost mklink enabled_Farms path\to\target\Farms​

       

      • Verify (git status) and commit (git add then git commit) the symlinks using Git for Windows.
      • Avoid mixing WSL and Windows-native tools for symlink management. If you’re using WSL, note that symlinks created in WSL most likely will not be compatible with Windows-native tools like Git for Windows. To avoid this:
        • Ensure that the symlinks are created in the Windows file system (not inside the WSL-specific file system).
        • Use Git for Windows to manage the repository instead of WSL’s Git.
       
       
        kautuk_sahni
        Community Manager
        kautuk_sahniCommunity Manager
        Community Manager
        March 4, 2025

        @georhe6 Did you find the suggestions helpful? Please let us know if you need more information. If a response worked, kindly mark it as correct for posterity; alternatively, if you found a solution yourself, we’d appreciate it if you could share it with the community. Thank you!

        Kautuk Sahni
        Terms & ConditionsAccessibility statement

        Loading footer...