Uploaded image for project: 'Syncope'
  1. Syncope
  2. SYNCOPE-1345

domain configuration files do not persist across docker reloads

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Not A Problem
    • Affects Version/s: 2.0.9, 2.1.0
    • Fix Version/s: None
    • Component/s: docker
    • Labels:
      None

      Description

      When using docker images - if additional domains are configured, their configuration files must be manually copied to the docker image area )/var/lib/tomcat8/webapps/syncope/WEB-INF/classes/domains/) to be with the Master.* files that are processed when syncope-core starts up.

      If the docker image is upgraded or re-loaded (down + up) the configuration files for the additional domains are lost and must be manually copied over again and then the core must be restarted.

      It would be great if there was a way to retain the domain configurations in a volume mount or some other more persistent storage mechanism so that they are not lost when updating or re-initializing the image.

       

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              wyllys Wyllys Ingersoll
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: