[
https://issues.apache.org/jira/browse/SYNCOPE-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16558792#comment-16558792
]
Wyllys Ingersoll commented on SYNCOPE-1345:
-------------------------------------------
Disregard, the above method doesnt have any effect.
Instead of reading the domain info from /etc/apache-syncope/domains, the core
module only appears to look in $CLASSPATH:/domains
(/var/lib/tomcat8/webapps/syncope/WEB-INF/classes/domains).
I can copy the new domain files to any location I want with the startup script,
but that seems kind of ugly.
Should there be (or is there already) a better way to configure a location for
domains other than Master?
> domain configuration files do not persist across docker reloads
> ---------------------------------------------------------------
>
> Key: SYNCOPE-1345
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1345
> Project: Syncope
> Issue Type: Improvement
> Components: docker
> Affects Versions: 2.0.9, 2.1.0
> Reporter: Wyllys Ingersoll
> Priority: Minor
>
> 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.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
