Multi site functionality

Comments

5 comments

  • Janne Peltola

    UPDATE

    I think I have found one way of doing this: First I need to create a script that exports all site folders from PDQ Deploy to xml format, then run script that replaces the default $(Repository) variable with @(folderspecificvariable) and then run script that imports those xml's back to PDQ Deploy.

    Any comments on that approach?

    0
    Comment actions Permalink
  • Christian Bacher

    I understand that you reject the host file changes, but what are your concerns against a DFS share?
    It's working great here on 9 sites without any issues at all.

    0
    Comment actions Permalink
  • Janne Peltola

    Basically DFS doesn't solve the problem how to manage jobs inside PDQ. DFS can solve file replication issue (or just plain robocopy) but I would like to get that functionality inside PDQ as well so I could have site specific folders in Deploy and all jobs in that folder automatically could point to thats sites local fileshare.

    0
    Comment actions Permalink
  • Christian Bacher

    What about:

    Put all site specific Folders in the global (DFS) share, copy the steps in the deployment so you have 1 step for each site and use the condition tab (like, only deploy if target ist member of Collection site A, Site B etc.).

    That should solve the Problem with site specific steps inside a deployment.
    Thats my way with side specific files, registry entrys or Office deployments.

    1
    Comment actions Permalink
  • Janne Peltola

    Thats sounds interesting. I have to look into that more. Thanks!

    0
    Comment actions Permalink

Please sign in to leave a comment.